Triple
T8244726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C.V. |
E192821
|
entity |
| Predicate | workStructureRole |
P50478
|
FINISHED |
| Object | introductory life narrative in On Writing |
—
|
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: introductory life narrative in On Writing | Statement: [C.V., workStructureRole, introductory life narrative in On Writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workStructureRole Context triple: [C.V., workStructureRole, introductory life narrative in On Writing]
-
A.
workStructure
chosen
Indicates how work is organized, arranged, or structured within or between entities.
-
B.
formRole
Indicates that an entity assumes, is assigned, or functions in a particular role within a specified context or structure.
-
C.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
D.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
E.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78711f5081909c2f357334491a07 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.