Triple
T15523810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feijenoord Stadion |
E369032
|
entity |
| Predicate | renownedAs |
P74359
|
FINISHED |
| Object | home ground of Feyenoord |
—
|
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: home ground of Feyenoord | Statement: [Feijenoord Stadion, renownedAs, home ground of Feyenoord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renownedAs Context triple: [Feijenoord Stadion, renownedAs, home ground of Feyenoord]
-
A.
celebratedAs
chosen
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
D.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
E.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04143bda08190a2dee44918c1ad1c |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.