Triple
T25906007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanderers |
E652751
|
entity |
| Predicate | hasOfficialNameStyle |
P39478
|
FINISHED |
| Object | HFX Wanderers Football Club |
—
|
NE NERFINISHED |
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: HFX Wanderers Football Club | Statement: [Wanderers, hasOfficialNameStyle, HFX Wanderers Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialNameStyle Context triple: [Wanderers, hasOfficialNameStyle, HFX Wanderers Football Club]
-
A.
hasOfficialStyle
Indicates that an entity possesses a formally recognized style, manner, or form as defined by an authoritative source or standard.
-
B.
hasOfficialNameContaining
Indicates that an entity’s official name includes a specified substring or sequence of characters.
-
C.
hasOfficialDualNameWith
Indicates that two entities share an officially recognized dual or joint name used in formal contexts.
-
D.
nameStyle
chosen
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
E.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:27 a.m.