Triple
T6168528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvey Cheyne |
E137632
|
entity |
| Predicate | learnsValueOf |
P69185
|
FINISHED |
| Object | work |
—
|
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: work | Statement: [Harvey Cheyne, learnsValueOf, work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: learnsValueOf Context triple: [Harvey Cheyne, learnsValueOf, work]
-
A.
valueOfL
Indicates that one entity represents the numerical or quantitative value associated with another entity, typically in a specific context or measurement.
-
B.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
C.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
D.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
E.
valueExpressed
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d8de56481909583104c70a52616 |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.