Triple
T27945639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPX |
E700871
|
entity |
| Predicate | reliabilityScope |
P163984
|
FINISHED |
| Object | between two endpoints |
—
|
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: between two endpoints | Statement: [SPX, reliabilityScope, between two endpoints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliabilityScope Context triple: [SPX, reliabilityScope, between two endpoints]
-
A.
guaranteeScope
Indicates that one entity defines or limits the extent, conditions, or coverage under which a guarantee provided by another entity is valid.
-
B.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
C.
certificationScope
Indicates the specific range, domain, or subject matter that a given certification covers or applies to.
-
D.
scopeOfReference
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
E.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 7:21 p.m.