Triple
T25839114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ötzi the Iceman |
E650884
|
entity |
| Predicate | bodyCompleteness |
P159336
|
FINISHED |
| Object | nearly complete |
—
|
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: nearly complete | Statement: [Ötzi the Iceman, bodyCompleteness, nearly complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyCompleteness Context triple: [Ötzi the Iceman, bodyCompleteness, nearly complete]
-
A.
bodyOutcome
Indicates the resulting physical state or condition that occurs to a body as a consequence of an action or event.
-
B.
inscriptionCompleteness
Indicates how fully or partially an inscription is preserved or recorded in relation to its original state.
-
C.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
D.
manuscriptCompleteness
Indicates the degree to which a manuscript is fully developed, with all required sections, content, and components present and finalized.
-
E.
isIncompletenessSubjectTo
Indicates that an incompleteness, deficiency, or lack in something is governed, constrained, or determined by a particular condition, rule, or authority.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f80b9c8190947c4542654455a6 |
completed | May 2, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:49 a.m.