Triple
T38659497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinn Morgendorffer |
E939989
|
entity |
| Predicate | oftenDeniesRelationTo |
P192795
|
FINISHED |
| Object | Daria Morgendorffer |
E492826
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Daria Morgendorffer | Statement: [Quinn Morgendorffer, oftenDeniesRelationTo, Daria Morgendorffer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDeniesRelationTo Context triple: [Quinn Morgendorffer, oftenDeniesRelationTo, Daria Morgendorffer]
-
A.
hasAllegedRelationshipWith
Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
-
B.
oftenDeniesOrDownplays
chosen
Indicates that one entity frequently rejects, minimizes, or dismisses the significance or validity of another entity, event, or claim.
-
C.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
D.
typicallyDenies
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another entity.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205bc44908190a2f5f1d897cc1bff |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.