Triple
T26967421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Precourt Sports Ventures |
E679207
|
entity |
| Predicate | attemptedToRelocate |
P109067
|
FINISHED |
| Object | Columbus Crew SC to Austin, Texas |
—
|
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: Columbus Crew SC to Austin, Texas | Statement: [Precourt Sports Ventures, attemptedToRelocate, Columbus Crew SC to Austin, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedToRelocate Context triple: [Precourt Sports Ventures, attemptedToRelocate, Columbus Crew SC to Austin, Texas]
-
A.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
B.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
C.
proposesRelocationTo
chosen
Indicates that one entity suggests or recommends that another entity move or be moved to a different location.
-
D.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
E.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621222ea88190a58d686d3b4cc802 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:36 a.m.