Triple
T1683807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIAU |
E36396
|
entity |
| Predicate | governedDomain |
P4800
|
FINISHED |
| Object | interuniversity athletics |
—
|
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: interuniversity athletics | Statement: [CIAU, governedDomain, interuniversity athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedDomain Context triple: [CIAU, governedDomain, interuniversity athletics]
-
A.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
B.
regulatoryDomain
chosen
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
C.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
-
D.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
E.
governmentalDomain
Indicates that one entity functions as the governmental sphere, jurisdiction, or area of authority within which another entity operates or is regulated.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.