Triple
T32924556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | global Bahá’í community |
E842231
|
entity |
| Predicate | hasWorldCentreIn |
P93967
|
FINISHED |
| Object | Haifa, Israel |
—
|
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: Haifa, Israel | Statement: [global Bahá’í community, hasWorldCentreIn, Haifa, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldCentreIn Context triple: [global Bahá’í community, hasWorldCentreIn, Haifa, Israel]
-
A.
hasWorldCentre
Indicates that something possesses or contains a central focal point or main hub within a particular world or global context.
-
B.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
C.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
D.
hasCentralLandmark
Indicates that a place or area contains a primary or defining landmark located at or near its center.
-
E.
hasCenterIn
chosen
Indicates that something is located, based, or primarily focused within a specified central place or area.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, 1:20 a.m.