Triple
T26467702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farewell to the Sacred Mosque |
E665812
|
entity |
| Predicate | performedOnFoot |
P170352
|
FINISHED |
| Object | usually |
—
|
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: usually | Statement: [Farewell to the Sacred Mosque, performedOnFoot, usually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedOnFoot Context triple: [Farewell to the Sacred Mosque, performedOnFoot, usually]
-
A.
hasFootUsed
Indicates that an entity uses a particular foot (or feet) to perform an action or function.
-
B.
hasFootCrossing
Indicates that one entity has a designated crossing point specifically intended for pedestrians on foot.
-
C.
footMorphologySuggests
Indicates that the structure or shape of a foot provides evidence or clues pointing toward a particular characteristic, behavior, or classification.
-
D.
hasSettlementAtFoot
Indicates that a settlement is located at the base or lower slopes of a geographic feature such as a hill or mountain.
-
E.
bearerDidNotRunBarefootIn
Indicates that the bearer did not run barefoot in the specified location or during the specified event or time period.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 12:17 a.m.