Triple
T37514171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldeum Desert |
E932590
|
entity |
| Predicate | travelCondition |
P87607
|
FINISHED |
| Object | dangerous to cross |
—
|
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 to cross | Statement: [Caldeum Desert, travelCondition, dangerous to cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelCondition Context triple: [Caldeum Desert, travelCondition, dangerous to cross]
-
A.
travelCharacteristic
chosen
Indicates a quality, feature, or attribute that characterizes how travel or movement is conducted or experienced.
-
B.
travelRequirement
Indicates that a certain amount or type of travel is necessary for participating in or fulfilling the associated activity, role, or arrangement.
-
C.
travelProtection
Indicates that one entity provides or is covered by protection, insurance, or safeguards specifically related to travel activities or trips.
-
D.
travelRuling
Indicates a legal or authoritative decision that determines whether, how, or under what conditions travel may occur.
-
E.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.