Triple
T27186158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Phelps |
E683336
|
entity |
| Predicate | desiredRelocationCity |
P100317
|
FINISHED |
| Object | Miami, Florida |
—
|
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: Miami, Florida | Statement: [Rachel Phelps, desiredRelocationCity, Miami, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: desiredRelocationCity Context triple: [Rachel Phelps, desiredRelocationCity, Miami, Florida]
-
A.
relocatedWithinCity
Indicates that an entity moved from one location to another within the same city.
-
B.
cityAfterRelocation
chosen
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
C.
mayRelocateTo
Indicates that an entity has the possibility or permission to move or be moved from its current location to another specified location.
-
D.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
-
E.
cityRelocationStatus
Indicates the status or stage of a city’s relocation process from one place 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62580d96c8190a958383f732a5b90 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:30 a.m.