Triple
T14689398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Neck |
E344998
|
entity |
| Predicate | travelDifficulty |
P2406
|
FINISHED |
| Object | dangerous for large armies |
—
|
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: dangerous for large armies | Statement: [The Neck, travelDifficulty, dangerous for large armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelDifficulty Context triple: [The Neck, travelDifficulty, dangerous for large armies]
-
A.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
difficulty
chosen
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
C.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
D.
hasRecreationDifficulty
Indicates the level of challenge or effort required to engage in a particular recreational activity or experience.
-
E.
difficultySource
Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.