Triple
T26377761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REM (Road Experience Management) |
E660944
|
entity |
| Predicate | mapContent |
P158079
|
FINISHED |
| Object | static road infrastructure |
—
|
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: static road infrastructure | Statement: [REM (Road Experience Management), mapContent, static road infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapContent Context triple: [REM (Road Experience Management), mapContent, static road infrastructure]
-
A.
cartographicContent
chosen
Indicates that the resource contains or is associated with map-related or cartographic information.
-
B.
mapsIncluded
Indicates that one map or mapping is contained within, or is a subset of, another map or mapping.
-
C.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
D.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
-
E.
mapsIn
Indicates that one entity is contained or represented within another entity as part of a mapping or map-like relationship.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:02 p.m.