Triple
T11060543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2 John |
E261494
|
entity |
| Predicate | openingGreetingFrom |
P97576
|
FINISHED |
| Object | the elder |
—
|
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: the elder | Statement: [2 John, openingGreetingFrom, the elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingGreetingFrom Context triple: [2 John, openingGreetingFrom, the elder]
-
A.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
-
B.
openingAnswer
Indicates that an entity provides an initial or first response in a dialogue, interaction, or sequence of answers.
-
C.
openingLine
Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
-
D.
openingNarrationBy
Indicates that an entity serves as the narrator delivering the opening narration for another entity (such as a work or production).
-
E.
openingCatchphrase
Indicates that one entity is a characteristic phrase or line regularly used by another entity at the beginning of a recurring performance, appearance, or communication.
- F. None of above. chosen
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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798e991848190b07c2f48dae38681 |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.