Triple
T10144007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UR-100 |
E231655
|
entity |
| Predicate | cep |
P92495
|
FINISHED |
| Object | about 1.5 km |
—
|
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: about 1.5 km | Statement: [UR-100, cep, about 1.5 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cep Context triple: [UR-100, cep, about 1.5 km]
-
A.
CEP
Indicates a relationship where one entity serves as the central or primary point (e.g., center, hub, or focal element) in relation to another entity or set of entities.
-
B.
usesEchoCancellation
Indicates that an entity employs echo cancellation techniques to reduce or eliminate echo in audio communication.
-
C.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
D.
via
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
E.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb28a1708190b46499dbe51a694a |
completed | April 2, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.