Triple
T16966363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J.F. Lehman & Company |
E411547
|
entity |
| Predicate | valueCreationApproach |
P44332
|
FINISHED |
| Object | operational improvement |
—
|
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: operational improvement | Statement: [J.F. Lehman & Company, valueCreationApproach, operational improvement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueCreationApproach Context triple: [J.F. Lehman & Company, valueCreationApproach, operational improvement]
-
A.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
B.
creationType
chosen
Indicates the manner or process by which something was brought into existence or produced.
-
C.
supportedCreationOf
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment of another entity.
-
D.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
E.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a548b48190b87468630f3e3209 |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.