Triple
T24915202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munster Rugby |
E623963
|
entity |
| Predicate | secondaryHomeCity |
P48850
|
FINISHED |
| Object | Cork |
—
|
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: Cork | Statement: [Munster Rugby, secondaryHomeCity, Cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryHomeCity Context triple: [Munster Rugby, secondaryHomeCity, Cork]
-
A.
hasSecondaryCity
chosen
Indicates that an entity possesses or is associated with a secondary city in addition to its primary city.
-
B.
secondarySeeCity
Indicates that an entity has a secondary or less prominent association with a particular city.
-
C.
secondaryCityTerminus
Indicates that a city serves as a secondary (non-primary) terminus or endpoint for a given route or line.
-
D.
secondMetropolitan
Indicates that one entity is the second metropolitan (e.g., second-ranking or second-designated metropolitan authority or see) in relation to another entity.
-
E.
secondaryCapital
Indicates that a location serves as an additional or secondary capital city for a political entity, alongside its primary capital.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 5:28 a.m.