Triple
T10655830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | road from Jerusalem to Jericho |
E251084
|
entity |
| Predicate | dangerInAntiquity |
P95189
|
FINISHED |
| Object | robbery |
—
|
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: robbery | Statement: [road from Jerusalem to Jericho, dangerInAntiquity, robbery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dangerInAntiquity Context triple: [road from Jerusalem to Jericho, dangerInAntiquity, robbery]
-
A.
historicalPeriodOfGreatestDanger
Indicates the time period in which an entity faced its highest level of risk, threat, or vulnerability.
-
B.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
C.
reputationInAntiquity
Indicates the reputation or standing an entity had during ancient times.
-
D.
heritageThreat
Indicates that an entity poses a risk of damage, loss, or degradation to cultural, historical, or natural heritage.
-
E.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dffa73a08190bf661df600b4ab96 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:07 p.m.