Triple
T3216121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-90 hill |
E67398
|
entity |
| Predicate | kPoint |
P15212
|
FINISHED |
| Object | 90 m |
—
|
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: 90 m | Statement: [K-90 hill, kPoint, 90 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kPoint Context triple: [K-90 hill, kPoint, 90 m]
-
A.
KPoint
Indicates a relationship where a specific point is designated or identified as a key or reference point within a spatial or geometric context.
-
B.
hasKPoint
chosen
Indicates that an entity possesses or is associated with a specific K-point, typically a designated point in reciprocal or parameter space.
-
C.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
-
D.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
E.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab096b588190b22e41a76263ae92 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:07 p.m.