Triple
T2998498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graham-Newman Corporation |
E81127
|
entity |
| Predicate | employedStrategy |
P13064
|
FINISHED |
| Object | margin of safety |
—
|
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: margin of safety | Statement: [Graham-Newman Corporation, employedStrategy, margin of safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedStrategy Context triple: [Graham-Newman Corporation, employedStrategy, margin of safety]
-
A.
employedApproximately
Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
-
B.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
C.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
D.
peakEmployment
Indicates that an entity has reached its highest level of employment or workforce size during a specified period.
-
E.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.