Triple
T9754966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Elinor |
E236531
|
entity |
| Predicate | relationshipWithMerida |
P89053
|
FINISHED |
| Object | strained at beginning of film |
—
|
LITERAL 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: strained at beginning of film | Statement: [Queen Elinor, relationshipWithMerida, strained at beginning of film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithMerida Context triple: [Queen Elinor, relationshipWithMerida, strained at beginning of film]
-
A.
relationshipToEsmeralda
Indicates the specific type of relationship or connection an entity has to Esmeralda.
-
B.
relationshipToPrincess
chosen
Indicates the specific familial, social, or romantic connection that one entity has to a princess.
-
C.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
D.
partnerInMyth
Indicates a mythological relationship in which two entities are partners or companions within the same myth or mythic narrative.
-
E.
relationshipToPetra
Indicates the specific type of relationship or connection that one entity has to Petra.
- F. None of above.
Provenance (3 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb1370c8190bc153db8cababc62 |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.