Triple
T31988018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebor Gabála Érenn |
E816787
|
entity |
| Predicate | associatesWithDeity |
P69792
|
FINISHED |
| Object | Yahweh |
E475905
|
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: Yahweh | Statement: [Lebor Gabála Érenn, associatesWithDeity, Yahweh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatesWithDeity Context triple: [Lebor Gabála Érenn, associatesWithDeity, Yahweh]
-
A.
associatedWithGod
chosen
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
B.
closelyAssociatedDeity
Indicates a deity that is strongly connected or frequently linked to another entity, such as a person, place, object, or concept, through special association or significance.
-
C.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
D.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
E.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb15784348190a40b784ea4de7f0d |
completed | June 14, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:12 a.m.