Triple
T568139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John and Eline Goss |
E13601
|
entity |
| Predicate | honoredThrough |
P15675
|
FINISHED |
| Object | stadium naming |
—
|
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: stadium naming | Statement: [John and Eline Goss, honoredThrough, stadium naming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoredThrough Context triple: [John and Eline Goss, honoredThrough, stadium naming]
-
A.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
B.
honour
Indicates showing respect, admiration, or recognition toward someone or something, often through actions, words, or ceremonial acknowledgment.
-
C.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
D.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
E.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.