Triple
T28537546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TA-90 Index |
E722204
|
entity |
| Predicate | indexFamilyPeer |
P137284
|
FINISHED |
| Object | TA-35 Index |
—
|
NE NERFINISHED |
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: TA-35 Index | Statement: [TA-90 Index, indexFamilyPeer, TA-35 Index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexFamilyPeer Context triple: [TA-90 Index, indexFamilyPeer, TA-35 Index]
-
A.
isPartOfIndexFamily
chosen
Indicates that one index belongs to, or is a member of, a larger index family or collection of related indexes.
-
B.
baseIndexFamily
Indicates that one entity serves as the primary or reference index set upon which a family of related indexed entities is defined or organized.
-
C.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
D.
indexStructure
Indicates that one entity serves as an index or organizational framework that structures, arranges, or provides access to another entity or set of entities.
-
E.
indexUsedBy
Indicates that a particular index is utilized or referenced by another entity, such as a query, process, or data structure.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:33 a.m.