Triple
T4780890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | outer Solar System |
E106160
|
entity |
| Predicate | hasUncertainOuterBoundary |
P59279
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [outer Solar System, hasUncertainOuterBoundary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainOuterBoundary Context triple: [outer Solar System, hasUncertainOuterBoundary, true]
-
A.
hasUncertainBoundary
Indicates that the boundary or extent of something is not clearly defined, fixed, or precisely known.
-
B.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
C.
hasOuterRingComponent
Indicates that an entity includes another entity as a component specifically located in its outer ring.
-
D.
hasBoundarySystem
Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
-
E.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6922407481908565ed0b1dac2b30 |
completed | March 20, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:21 p.m.