Triple
T30107090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huluppu tree |
E765161
|
entity |
| Predicate | cleansedBy |
P32290
|
FINISHED |
| Object | Gilgamesh |
—
|
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: Gilgamesh | Statement: [Huluppu tree, cleansedBy, Gilgamesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleansedBy Context triple: [Huluppu tree, cleansedBy, Gilgamesh]
-
A.
cleaningAction
chosen
Indicates an action in which an agent removes dirt, impurities, or unwanted substances from a target object, area, or entity.
-
B.
hasCleanlinessLevel
Indicates the degree or state of cleanliness associated with an entity.
-
C.
cleanSweep
Indicates achieving a complete and flawless victory or success in all parts of a competition, task, or series, leaving no losses or omissions.
-
D.
clearedOf
Indicates that an entity has been officially found not responsible for, or freed from suspicion of, a previously alleged wrongdoing, charge, or negative condition.
-
E.
cleared
Indicates that an entity has removed obstacles, doubts, or restrictions from another entity or from a particular state or situation.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dbaf34c8190b9ce6f3d9cbad03d |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:09 p.m.