Triple
T24083217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Jones |
E596562
|
entity |
| Predicate | hasEditorialOfficeIn |
P108902
|
FINISHED |
| Object | San Francisco |
—
|
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: San Francisco | Statement: [Mother Jones, hasEditorialOfficeIn, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditorialOfficeIn Context triple: [Mother Jones, hasEditorialOfficeIn, San Francisco]
-
A.
editorialOffice
chosen
Indicates that an entity serves as or is associated with the editorial office responsible for managing editorial processes (such as review, editing, and publication decisions) for another entity.
-
B.
hasEditorialMission
Indicates that an entity maintains or follows a defined editorial mission or guiding editorial policy.
-
C.
hasPublicationPlace
Indicates the place or location where a publication was produced, issued, or made publicly available.
-
D.
hasPublisherHeadquartersIn
Indicates that the main corporate headquarters of a publishing entity is located in a specified place.
-
E.
hasEditorialBoard
Indicates that an entity (such as a publication or journal) is overseen or governed by a specific editorial board.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc257f408190ab87c6f95adca96d |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.