Triple
T33613366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayt Allah |
E861047
|
entity |
| Predicate | primaryReferentName |
P59207
|
FINISHED |
| Object | Kaaba |
E6838
|
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: Kaaba | Statement: [Bayt Allah, primaryReferentName, Kaaba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReferentName Context triple: [Bayt Allah, primaryReferentName, Kaaba]
-
A.
primaryReferent
chosen
Indicates that one entity is the main or most salient referent associated with another entity among potentially multiple candidates.
-
B.
primaryName
Indicates that the associated name is the main or most commonly used name for the entity in question.
-
C.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
D.
primaryAlias
Indicates that one alias is the main or preferred name used to refer to an entity among its possible alternative names.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- 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_6a366e7f1aec81909c1fecb872816f21 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.