Triple
T10744347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPHL |
E253411
|
entity |
| Predicate | hasOfficials |
P11211
|
FINISHED |
| Object | referees and linesmen |
—
|
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: referees and linesmen | Statement: [SPHL, hasOfficials, referees and linesmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficials Context triple: [SPHL, hasOfficials, referees and linesmen]
-
A.
hasOfficial
chosen
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
B.
hasOfficialAdministration
Indicates that an entity is formally governed, managed, or overseen by an official administrative body or authority.
-
C.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
D.
hasOfficialSpokespersons
Indicates that an entity is formally represented or spoken for by one or more designated spokespersons in an official capacity.
-
E.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b6b4b48190bad08500fa963062 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.