Triple
T33613358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayt Allah |
E861047
|
entity |
| Predicate | locationOfPrimaryReferent |
P76038
|
FINISHED |
| Object | Mecca |
E6835
|
NE 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: Mecca | Statement: [Bayt Allah, locationOfPrimaryReferent, Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfPrimaryReferent Context triple: [Bayt Allah, locationOfPrimaryReferent, Mecca]
-
A.
primaryReferent
Indicates that one entity is the main or most salient referent associated with another entity among potentially multiple candidates.
-
B.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
C.
locationOfRepresentation
Indicates that one entity is the place or site where another entity is depicted, displayed, or represented.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
- F. None of above.
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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3627119fe081909449fd8b78f76171 |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.