Triple
T14416653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanna Schmitz |
E357469
|
entity |
| Predicate | actuallyUnableTo |
P17604
|
FINISHED |
| Object | write the camp report |
—
|
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: write the camp report | Statement: [Hanna Schmitz, actuallyUnableTo, write the camp report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuallyUnableTo Context triple: [Hanna Schmitz, actuallyUnableTo, write the camp report]
-
A.
cannot
chosen
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
B.
cannotExpress
Indicates that one entity is unable to convey, articulate, or communicate something (such as a feeling, idea, or message) to another entity.
-
C.
cannotForm
Indicates that one entity is unable or not permitted to establish, create, or constitute a specified relationship, structure, or configuration with another entity.
-
D.
failsTo
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
E.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:17 a.m.