Triple
T24307971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | burial of Aminah bint Wahb |
E612584
|
entity |
| Predicate | hasAssociatedRoute |
P4374
|
FINISHED |
| Object | Mecca–Yathrib caravan route |
—
|
NE NERFINISHED |
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: Mecca–Yathrib caravan route | Statement: [burial of Aminah bint Wahb, hasAssociatedRoute, Mecca–Yathrib caravan route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedRoute Context triple: [burial of Aminah bint Wahb, hasAssociatedRoute, Mecca–Yathrib caravan route]
-
A.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasComponentRoute
Indicates that one route includes another route as a constituent or subordinate part of its overall structure.
-
C.
hasPrimaryRoute
Indicates that one entity is designated as the main or principal route associated with another entity.
-
D.
hasCommonRoute
Indicates that two or more entities share at least one overlapping or identical route or path.
-
E.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922821248190a1b274f839251ddc |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:31 a.m.