Triple
T5331623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont-Saint-Michel |
E123322
|
entity |
| Predicate | causewayType |
P62869
|
FINISHED |
| Object | elevated bridge causeway |
—
|
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: elevated bridge causeway | Statement: [Mont-Saint-Michel, causewayType, elevated bridge causeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causewayType Context triple: [Mont-Saint-Michel, causewayType, elevated bridge causeway]
-
A.
guidewayType
Indicates the specific kind or classification of guideway used in a transportation or movement system.
-
B.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
-
C.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
hasCarriagewayType
Indicates the specific structural or functional type of carriageway associated with a road segment (e.g., single, dual, or other carriageway configurations).
-
E.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85aab0308190990626cbc9da3e21 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.