Triple
T27137321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleischer Studios |
E681723
|
entity |
| Predicate | laterLocationCity |
P42649
|
FINISHED |
| Object | Miami |
—
|
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 | Statement: [Fleischer Studios, laterLocationCity, Miami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLocationCity Context triple: [Fleischer Studios, laterLocationCity, Miami]
-
A.
laterLocation
chosen
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
B.
hasLocationCity
Indicates that an entity is situated in, occurs in, or is associated with a specific city as its location.
-
C.
destinationCity
Indicates the city to which an entity is traveling, being sent, or ultimately directed.
-
D.
primaryLocationCity
Indicates the city that serves as the main or primary location associated with the subject.
-
E.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 27, 2026, 9:07 a.m.