Triple
T8886312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protarchus |
E211539
|
entity |
| Predicate | positionInDialogue |
P56087
|
FINISHED |
| Object | younger interlocutor |
—
|
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: younger interlocutor | Statement: [Protarchus, positionInDialogue, younger interlocutor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInDialogue Context triple: [Protarchus, positionInDialogue, younger interlocutor]
-
A.
dialoguePosition
chosen
Indicates the relative placement or ordering of an utterance or turn within a dialogue or conversational sequence.
-
B.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
C.
dialogueLine
Indicates that one entity is a specific spoken or written line of dialogue expressed by another entity (such as a character or speaker).
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618bd30881909e54d0708f144786 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.