Triple
T26878775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Ground |
E676827
|
entity |
| Predicate | isHistoricHomeGroundOf |
P138386
|
FINISHED |
| Object | Nottingham Forest F.C. |
—
|
NE NERFINISHED |
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: Nottingham Forest F.C. | Statement: [City Ground, isHistoricHomeGroundOf, Nottingham Forest F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricHomeGroundOf Context triple: [City Ground, isHistoricHomeGroundOf, Nottingham Forest F.C.]
-
A.
hasHistoricGround
chosen
Indicates that one entity is located on, associated with, or includes land or grounds of historical significance related to another entity.
-
B.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
C.
hasHistoricBasisIn
Indicates that something is grounded in, derived from, or justified by historical events, practices, or precedents.
-
D.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
E.
hasHomeRegionHistorical
Indicates that an entity is historically associated with or originates from a particular home region.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f1a5f9881908a7d4ff6e5f783ca |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:37 a.m.