Triple
T26869928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Aeros (WHA) |
E676581
|
entity |
| Predicate | attemptedRelocationTo |
P1660
|
FINISHED |
| Object | Denver, Colorado |
—
|
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: Denver, Colorado | Statement: [Houston Aeros (WHA), attemptedRelocationTo, Denver, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedRelocationTo Context triple: [Houston Aeros (WHA), attemptedRelocationTo, Denver, Colorado]
-
A.
laterRelocationDestination
Indicates that a location serves as the destination of a subsequent relocation event for an entity, occurring after an earlier move.
-
B.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
C.
proposesRelocationTo
Indicates that one entity suggests or recommends that another entity move or be moved to a different location.
-
D.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
E.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e9aab488190b4dfd2fdb9631f1f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:31 a.m.