Triple
T28442683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris May |
E715753
|
entity |
| Predicate | employerCity |
P24431
|
FINISHED |
| Object | St. Louis, Missouri |
—
|
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: St. Louis, Missouri | Statement: [Chris May, employerCity, St. Louis, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerCity Context triple: [Chris May, employerCity, St. Louis, Missouri]
-
A.
majorEmployerCity
Indicates that a city is a primary or significant employer of a given entity (such as an organization or population).
-
B.
workCity
chosen
Indicates the city in which an entity (typically a person) performs their work or job.
-
C.
projectCity
Indicates that a project is located in, associated with, or primarily takes place within a specific city.
-
D.
cityIs
Indicates that one entity is a city associated with, or identified as, another entity.
-
E.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 1:47 a.m.