Triple
T34430622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill 16 terrace |
E883816
|
entity |
| Predicate | homeSupportBaseFor |
P34846
|
FINISHED |
| Object | Dublin GAA |
—
|
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: Dublin GAA | Statement: [Hill 16 terrace, homeSupportBaseFor, Dublin GAA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeSupportBaseFor Context triple: [Hill 16 terrace, homeSupportBaseFor, Dublin GAA]
-
A.
homeBaseOf
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
-
B.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
C.
homeSupporterEnd
Indicates that one entity is the home supporter at the conclusion or end point of a specified event or period.
-
D.
IndependentSupportBase
Indicates that one entity serves as a foundational, self-sufficient support structure for another, not relying on additional supports or connections.
-
E.
mainSupportBase
chosen
Indicates that one entity serves as the primary structural or functional support base for 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.