Triple
T4686548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharks (rugby union) |
E103933
|
entity |
| Predicate | foundedAsProvincialUnion |
P58793
|
FINISHED |
| Object | 1890 |
—
|
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: 1890 | Statement: [Sharks (rugby union), foundedAsProvincialUnion, 1890]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsProvincialUnion Context triple: [Sharks (rugby union), foundedAsProvincialUnion, 1890]
-
A.
formerProvince
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
-
B.
wasOriginalProvinceOfCanadianConfederation
Indicates that an entity served as one of the founding provinces at the time of the original formation of the Canadian Confederation.
-
C.
formerProvinceMunicipality
Indicates that a municipality previously held the status of a province-level administrative unit but no longer does.
-
D.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
E.
establishedAsUnionTerritoryOn
Indicates the date or event on which a region was formally designated and constituted as a union territory.
- F. None of above. chosen
Provenance (4 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd660414b08190ab37467755d383b5 |
completed | March 20, 2026, 3:21 p.m. |
Created at: March 20, 2026, 1:16 p.m.