Triple
T8173445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norway U18 |
E190880
|
entity |
| Predicate | homeAssociationFoundedIn |
P81086
|
FINISHED |
| Object | 1902 |
—
|
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: 1902 | Statement: [Norway U18, homeAssociationFoundedIn, 1902]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAssociationFoundedIn Context triple: [Norway U18, homeAssociationFoundedIn, 1902]
-
A.
homeAssociation
Indicates a relationship where one entity is associated with, belongs to, or is linked as a home or primary place to another entity.
-
B.
hasNeighborhoodAssociation
Indicates that an entity is associated with, or falls under the jurisdiction of, a particular neighborhood association.
-
C.
countyAssociation
Indicates a relationship where an entity is associated with, belongs to, or is administered by a specific county.
-
D.
communityServicesDistrictFormationYear
Indicates the year in which a community services district was officially formed or established.
-
E.
committeeFoundedIn
Indicates that a committee was established or came into existence in a specific year or time period.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb48092b348190a37cb3746a434094 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb40a017608190b6b48cf60335fa8d |
completed | March 31, 2026, 3:33 a.m. |
Created at: March 30, 2026, 5:39 p.m.