Triple
T4472066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ape-man |
E98516
|
entity |
| Predicate | modifiedInto |
P43320
|
FINISHED |
| Object | part-human creature |
—
|
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: part-human creature | Statement: [Ape-man, modifiedInto, part-human creature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiedInto Context triple: [Ape-man, modifiedInto, part-human creature]
-
A.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
B.
setInto
Indicates placing or inserting one entity into another entity or context, often initiating a new state or condition.
-
C.
modification
chosen
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
D.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
E.
regeneratesInto
Indicates that one entity transforms or is restored into another entity, typically as a result of a regenerative process.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.