Triple
T24253095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prithvi-III |
E603586
|
entity |
| Predicate | typeOfRange |
P8771
|
FINISHED |
| Object | short-range |
—
|
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: short-range | Statement: [Prithvi-III, typeOfRange, short-range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRange Context triple: [Prithvi-III, typeOfRange, short-range]
-
A.
rangeType
chosen
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
nativeRangeType
Indicates the specific type or classification of the geographic area where an entity naturally occurs or originates.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8bcb1c8190995e464a5f85fba9 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.