Triple
T9662068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamhat |
E233612
|
entity |
| Predicate | purposeOfMission |
P53987
|
FINISHED |
| Object | to tame Enkidu |
—
|
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: to tame Enkidu | Statement: [Shamhat, purposeOfMission, to tame Enkidu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfMission Context triple: [Shamhat, purposeOfMission, to tame Enkidu]
-
A.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
B.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
C.
describesMissionOf
Indicates that one entity specifies, explains, or defines the mission or purpose of another entity.
-
D.
missionRationale
chosen
Indicates the underlying purpose, justification, or intended reason for undertaking a particular mission or operation.
-
E.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.