Triple
T9268329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principal Benjamin Krupp |
E222757
|
entity |
| Predicate | transformationReversal |
P12913
|
FINISHED |
| Object | water on the head |
—
|
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: water on the head | Statement: [Principal Benjamin Krupp, transformationReversal, water on the head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformationReversal Context triple: [Principal Benjamin Krupp, transformationReversal, water on the head]
-
A.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
B.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
C.
transformationResult
Indicates that one entity is the output or outcome produced by applying a transformation process to another entity.
-
D.
reversibility
chosen
Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
-
E.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd074d2d0081909f9f8db04547358e |
completed | April 1, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.