Triple
T37981187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southland rugby union team |
E947551
|
entity |
| Predicate | governingUnionFounded |
P72356
|
FINISHED |
| Object | 1887 |
—
|
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: 1887 | Statement: [Southland rugby union team, governingUnionFounded, 1887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingUnionFounded Context triple: [Southland rugby union team, governingUnionFounded, 1887]
-
A.
governingBodyFoundedIn
chosen
Indicates that a governing body was established or came into official existence in a specified year or time period.
-
B.
governingUnion
Indicates that one political or administrative entity serves as the primary governing authority over a union or collective of entities.
-
C.
confederationFounded
Indicates that a confederation was established or brought into existence at a particular time or by a particular founding event.
-
D.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
E.
countryGovernedFrom
Indicates that a country is administered or ruled from a specific city or location that serves as its seat of government.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.