Triple
T15030905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | stress–energy tensor |
E378339
|
entity |
| Predicate | componentIndexType |
P19875
|
FINISHED |
| Object | spacetime indices |
—
|
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: spacetime indices | Statement: [stress–energy tensor, componentIndexType, spacetime indices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentIndexType Context triple: [stress–energy tensor, componentIndexType, spacetime indices]
-
A.
isComponentOfIndex
Indicates that something functions as a specific indexed component or element within a larger structured whole.
-
B.
indexType
chosen
Indicates the classification or category of an index associated with an entity or structure.
-
C.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
D.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
E.
associatedIndex
Indicates that one entity is linked to another through a corresponding index or positional reference.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e2416081908dfba48d7f7b4a84 |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:59 a.m.