Triple
T28596209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CologneBlue skin |
E723776
|
entity |
| Predicate | navigationStyle |
P164895
|
FINISHED |
| Object | link-based navigation |
—
|
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: link-based navigation | Statement: [CologneBlue skin, navigationStyle, link-based navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationStyle Context triple: [CologneBlue skin, navigationStyle, link-based navigation]
-
A.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
B.
navigationSupport
Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
-
C.
naveStyle
Indicates the architectural style or design type applied specifically to the nave portion of a building or structure.
-
D.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
E.
navigationClass
Indicates that one entity serves as a navigation or menu grouping that organizes or links to another entity within a navigational structure.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:21 a.m.