Triple
T33580099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maslov index |
E860126
|
entity |
| Predicate | additiveUnder |
P4232
|
FINISHED |
| Object | concatenation of paths |
—
|
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: concatenation of paths | Statement: [Maslov index, additiveUnder, concatenation of paths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additiveUnder Context triple: [Maslov index, additiveUnder, concatenation of paths]
-
A.
isAdditiveFor
chosen
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
-
B.
additiveNotation
Indicates that something is expressed or represented using addition-based mathematical notation (e.g., using “+” and sums) rather than another form of representation.
-
C.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
D.
shiftedUnder
Indicates that one entity has been moved or displaced to a position beneath another entity.
-
E.
extendsUnder
Indicates that one entity physically stretches or reaches out beneath another entity, occupying a lower position while continuing under its span or area.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:40 a.m.