Triple
T23136689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomie |
E577341
|
entity |
| Predicate | canReproduceFrom |
P85855
|
FINISHED |
| Object | severed body parts |
—
|
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: severed body parts | Statement: [Tomie, canReproduceFrom, severed body parts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReproduceFrom Context triple: [Tomie, canReproduceFrom, severed body parts]
-
A.
hasReproduction
Indicates that one entity possesses or exhibits a particular mode, process, or capability of reproduction.
-
B.
hasReproductionType
chosen
Indicates the mode or method by which an entity reproduces or generates offspring.
-
C.
hasBeenReproducedIn
Indicates that something has been copied, replicated, or re-created in another medium, format, or context.
-
D.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
E.
overseesReproductionsOf
Indicates that one entity has responsibility for supervising, managing, or controlling the creation or production of copies or reproductions of another entity.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8c33308190a44f98a7aab3b670 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.