Triple
T30519954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eridu Genesis |
E776666
|
entity |
| Predicate | featuresHuman |
P93957
|
FINISHED |
| Object | Ziusudra |
—
|
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: Ziusudra | Statement: [Eridu Genesis, featuresHuman, Ziusudra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHuman Context triple: [Eridu Genesis, featuresHuman, Ziusudra]
-
A.
featuresPeople
Indicates that something prominently includes or showcases specific people as part of its content or presentation.
-
B.
featuresResponseOfPeople
Indicates a relationship where something presents or includes the reactions, opinions, or feedback expressed by people.
-
C.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
D.
featuresCharacterWith
chosen
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
E.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: April 29, 2026, 8:17 p.m.