Triple
T18156374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirabeau |
E434640
|
entity |
| Predicate | hasApproachCharacteristic |
P100986
|
FINISHED |
| Object | downhill approach |
—
|
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: downhill approach | Statement: [Mirabeau, hasApproachCharacteristic, downhill approach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachCharacteristic Context triple: [Mirabeau, hasApproachCharacteristic, downhill approach]
-
A.
hasApproachFeature
chosen
Indicates that something possesses a characteristic, element, or quality specifically related to its method, strategy, or manner of approach.
-
B.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
C.
hasApproachStructure
Indicates that one entity possesses or includes an approach structure that provides access or a path leading to another entity.
-
D.
hasApproachSide
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
E.
hasApproachTrail
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4debe27a88190bd76c6f78fcf1bd1 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.