Triple
T17121388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansari X Prize |
E415473
|
entity |
| Predicate | spaceBoundaryCriterion |
P68117
|
FINISHED |
| Object | 100 kilometers altitude |
—
|
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: 100 kilometers altitude | Statement: [Ansari X Prize, spaceBoundaryCriterion, 100 kilometers altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceBoundaryCriterion Context triple: [Ansari X Prize, spaceBoundaryCriterion, 100 kilometers altitude]
-
A.
hasBoundaryCriterion
chosen
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
B.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
E.
hasBoundarySystem
Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e809ee888190a2cf69d59c0b9c20 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.