Triple
T1355729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Connor |
E28982
|
entity |
| Predicate | workContext |
P36
|
FINISHED |
| Object | high-society milieu |
—
|
LITERAL FINISHED |
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: high-society milieu | Statement: [Mike Connor, workContext, high-society milieu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workContext Context triple: [Mike Connor, workContext, high-society milieu]
-
A.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
B.
workModel
Indicates that one entity serves as, or is based on, a particular model used for work, operation, or functional behavior.
-
C.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
D.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
E.
context
chosen
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c28c8dd0819082f94c9e7c837c5f |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.