Triple
T2578089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bancor |
E57023
|
entity |
| Predicate | valuationMethod |
P750
|
FINISHED |
| Object | linked to commodity prices |
—
|
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: linked to commodity prices | Statement: [Bancor, valuationMethod, linked to commodity prices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valuationMethod Context triple: [Bancor, valuationMethod, linked to commodity prices]
-
A.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
B.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
C.
evaluationFunction
Indicates a relationship where a specific procedure or rule assigns a value or score to an input, typically to assess its quality, utility, or desirability.
-
D.
assessmentMethod
chosen
Indicates the method or procedure used to evaluate, measure, or judge something.
-
E.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a86f9881908df29a7caaf9a7df |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.