Triple
T31943894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_tb |
E815594
|
entity |
| Predicate | hasIndexNotation |
P200205
|
FINISHED |
| Object | V_{tb} |
—
|
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: V_{tb} | Statement: [V_tb, hasIndexNotation, V_{tb}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndexNotation
Context triple: [V_tb, hasIndexNotation, V_{tb}]
-
A.
hasCoordinateBasis
Indicates that a coordinate system or vector space is associated with a specific basis that defines its coordinates.
-
B.
offsetNotation
Indicates that one representation specifies how far and in what way another representation is shifted or displaced from a reference point or baseline.
-
C.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
D.
hasIndexes
Indicates that an entity possesses one or more index structures or references used for organizing, locating, or accessing its associated data or elements.
-
E.
isVectorValued
Indicates that a function or expression returns a vector (multiple components) rather than a single scalar value.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: May 1, 2026, 12:06 a.m.