Triple
T27594165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zipkin |
E699849
|
entity |
| Predicate | hasUIFeature |
P182
|
FINISHED |
| Object | trace detail view |
—
|
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: trace detail view | Statement: [Zipkin, hasUIFeature, trace detail view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUIFeature Context triple: [Zipkin, hasUIFeature, trace detail view]
-
A.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
-
C.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63056c6a08190857baf73f58aa682 |
completed | May 2, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.