Triple
T33613364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayt Allah |
E861047
|
entity |
| Predicate | primaryReferentInstanceOf |
P205239
|
FINISHED |
| Object | cube-shaped building |
—
|
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: cube-shaped building | Statement: [Bayt Allah, primaryReferentInstanceOf, cube-shaped building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReferentInstanceOf Context triple: [Bayt Allah, primaryReferentInstanceOf, cube-shaped building]
-
A.
primaryReferent
Indicates that one entity is the main or most salient referent associated with another entity among potentially multiple candidates.
-
B.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
C.
referentRecord
Indicates that one record serves as a reference or pointer to another record within a data or information structure.
-
D.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
E.
principalSeeOf
Indicates that a principal has seen, reviewed, or visually examined a particular entity or item.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:41 a.m.