Triple
T23623294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arar crossing checkpoint |
E583380
|
entity |
| Predicate | servesTravelPurpose |
P102055
|
FINISHED |
| Object | Hajj pilgrimage |
—
|
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: Hajj pilgrimage | Statement: [Arar crossing checkpoint, servesTravelPurpose, Hajj pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTravelPurpose Context triple: [Arar crossing checkpoint, servesTravelPurpose, Hajj pilgrimage]
-
A.
validForTravelTo
Indicates that something (such as a document, item, or condition) is acceptable or authorized for use when traveling to a specified destination.
-
B.
journeyPurpose
chosen
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
C.
servesBusinessTravel
Indicates that an entity provides services or accommodations specifically intended for business-related travel.
-
D.
servesTravelersTo
Indicates a relationship where one entity provides services, assistance, or accommodations specifically directed toward travelers heading to a particular destination.
-
E.
bookingPurpose
Indicates the reason or intended use for which a booking or reservation is made.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17ae58c8190b7b6cdc57c6ead3a |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.