Triple
T38084293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig der Springer |
E950932
|
entity |
| Predicate | notableTypeOfEscape |
P207587
|
FINISHED |
| Object | prison escape |
—
|
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: prison escape | Statement: [Ludwig der Springer, notableTypeOfEscape, prison escape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTypeOfEscape Context triple: [Ludwig der Springer, notableTypeOfEscape, prison escape]
-
A.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
B.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
notableJourneyType
Indicates that there is a particularly significant or noteworthy type of journey associated with the subject.
-
D.
notableDeparture
Indicates that an entity has left a position, place, or role in a way that is significant or noteworthy.
-
E.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:21 p.m.