Triple
T1336730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Composite Index |
E28768
|
entity |
| Predicate | hasCalculationMethod |
P24421
|
FINISHED |
| Object | float-adjusted market capitalization |
—
|
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: float-adjusted market capitalization | Statement: [Nasdaq Composite Index, hasCalculationMethod, float-adjusted market capitalization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalculationMethod Context triple: [Nasdaq Composite Index, hasCalculationMethod, float-adjusted market capitalization]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
calculationType
chosen
Indicates the specific method, formula, or approach used to perform a calculation in the described relationship.
-
C.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
calculationProvider
Indicates that one entity serves as the source or performer of a calculation for another entity or process.
-
E.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1edda1c81909a1149b254b0d57e |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.