Triple
T21156619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halifax Thunderbirds |
E521327
|
entity |
| Predicate | usesArenaSurface |
P58186
|
FINISHED |
| Object | turf |
—
|
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: turf | Statement: [Halifax Thunderbirds, usesArenaSurface, turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArenaSurface Context triple: [Halifax Thunderbirds, usesArenaSurface, turf]
-
A.
usesSurface
chosen
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
B.
targetSurface
Indicates the surface or area that an action, effect, or object is directed at or intended to impact.
-
C.
associatedWithArena
Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
-
D.
hasLocalArena
Indicates that an entity possesses or is associated with an arena or venue located within its local area or jurisdiction.
-
E.
homeArenaUsed
Indicates that a particular arena serves as the primary home venue for a team or organization.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252c6db08190bcdffc3f2cfc6138 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.