Triple
T4483888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Synagogue of Oran |
E107188
|
entity |
| Predicate | functionCurrent |
P5507
|
FINISHED |
| Object | Muslim house of worship |
—
|
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: Muslim house of worship | Statement: [Great Synagogue of Oran, functionCurrent, Muslim house of worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionCurrent Context triple: [Great Synagogue of Oran, functionCurrent, Muslim house of worship]
-
A.
currentFunction
chosen
Indicates that an entity is presently serving in a specific role, position, or capacity.
-
B.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
C.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:58 p.m.