Triple
T31880976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylon (as Adad) |
E813882
|
entity |
| Predicate | functionInPantheon |
P177365
|
FINISHED |
| Object | regulator of weather |
—
|
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: regulator of weather | Statement: [Babylon (as Adad), functionInPantheon, regulator of weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInPantheon Context triple: [Babylon (as Adad), functionInPantheon, regulator of weather]
-
A.
projectFunction
Indicates that an entity serves as a function, role, or operational purpose within a project.
-
B.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
C.
functionInCitadel
Indicates that an entity serves a specific role or performs a particular function within a citadel.
-
D.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
E.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 30, 2026, 11:56 p.m.