Triple
T28406039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Toros |
E719529
|
entity |
| Predicate | relocationCountry |
P100958
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Miami Toros, relocationCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationCountry Context triple: [Miami Toros, relocationCountry, United States]
-
A.
countryOfRelocation
chosen
Indicates the country to which an entity has moved or been transferred from its original location.
-
B.
reassignmentCountry
Indicates a change in an entity’s associated country from one country to another, typically reflecting an official transfer or update of jurisdiction or affiliation.
-
C.
movedDomicileFromCountry
Indicates that an entity changed its place of residence from one specified country to another location.
-
D.
changedCountryAfter
Indicates that an entity moved from one country to another at some point after a specified reference time or event.
-
E.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d700f70819080f54d75296f8890 |
completed | May 2, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:23 a.m.