Triple
T14853279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel's Tomb |
E349284
|
entity |
| Predicate | hasSeparateAccessRoad |
P115874
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rachel's Tomb, hasSeparateAccessRoad, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparateAccessRoad Context triple: [Rachel's Tomb, hasSeparateAccessRoad, yes]
-
A.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
-
B.
isOnlyMajorRoadAccessTo
Indicates that one road is the sole major roadway providing access to a particular place or area.
-
C.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
D.
hasSeparateEntrances
Indicates that the related entities each have their own distinct entrance, rather than sharing a common one.
-
E.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44318f0819080b6c599f2d3474f |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.