Triple
T36657718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelóri |
E905037
|
entity |
| Predicate | hasNotableSubrange |
P3574
|
FINISHED |
| Object | Taniquetil |
E819717
|
NE 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: Taniquetil | Statement: [Pelóri, hasNotableSubrange, Taniquetil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSubrange Context triple: [Pelóri, hasNotableSubrange, Taniquetil]
-
A.
hasHighestSubrange
Indicates that one entity possesses or defines the subrange with the greatest extent or value relative to comparable subranges associated with another entity.
-
B.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
hasNotableSegment
chosen
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
D.
hasRangeNotation
Indicates that a value, property, or parameter is expressed using a range-style notation (e.g., lower and upper bounds) rather than as a single discrete value.
-
E.
hasMajorRange
Indicates that one entity encompasses or defines the primary or most extensive range or scope associated with another entity.
- F. None of above.
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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20cead00819094ef6393f7bd43d1 |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.