Triple
T18773138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Polar Spur |
E459064
|
entity |
| Predicate | hasUncertainDistance |
P132925
|
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: [North Polar Spur, hasUncertainDistance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainDistance Context triple: [North Polar Spur, hasUncertainDistance, true]
-
A.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
B.
hasUncertainNumber
Indicates that the associated quantity or count is not known precisely or cannot be determined with certainty.
-
C.
hasUncertainMedium
Indicates that the medium or material through which something is expressed, transmitted, or preserved is not clearly known or confidently identified.
-
D.
hasUncertainAffinityWith
Indicates a relationship where the strength, nature, or existence of affinity between two entities is unclear, variable, or not confidently established.
-
E.
hasUncertainNature
Indicates that the nature, status, or characteristics of the relationship or situation are not clearly defined, known, or determined.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.