Triple
T27293377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allison Hunt |
E688689
|
entity |
| Predicate | primaryConnectionInPlot |
P86630
|
FINISHED |
| Object | Owen Hunt's backstory |
—
|
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: Owen Hunt's backstory | Statement: [Allison Hunt, primaryConnectionInPlot, Owen Hunt's backstory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConnectionInPlot Context triple: [Allison Hunt, primaryConnectionInPlot, Owen Hunt's backstory]
-
A.
primaryConnections
chosen
Indicates that there exists a main or most significant relationship or linkage between entities, distinguishing these connections from secondary or peripheral ones.
-
B.
primaryFunctionInPlot
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
C.
primaryInteraction
Indicates the main or most significant interaction occurring between the involved entities.
-
D.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primaryMount
Indicates that one entity serves as the main or default mount (attachment or support point) for another entity.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 27, 2026, 11:17 a.m.