Triple
T37396334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brother Mouzone |
E928862
|
entity |
| Predicate | employerOrigin |
P192257
|
FINISHED |
| Object | New York |
—
|
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: New York | Statement: [Brother Mouzone, employerOrigin, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerOrigin Context triple: [Brother Mouzone, employerOrigin, New York]
-
A.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
B.
workOriginatesFrom
Indicates that the creation, development, or initiation of a work can be traced back to a particular source, agent, or origin.
-
C.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
D.
workforceOrigin
Indicates the source or place from which a workforce or labor force originates.
-
E.
employerService
Indicates that one entity provides employment-related services or functions to another entity, typically in the role of an employer.
- F. None of above. chosen
Provenance (4 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 3, 2026, 4:16 p.m.