Triple
T2911569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jericho-Trompete siren |
E63692
|
entity |
| Predicate | laterModification |
P42870
|
FINISHED |
| Object | often removed from later Ju 87 variants |
—
|
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: often removed from later Ju 87 variants | Statement: [Jericho-Trompete siren, laterModification, often removed from later Ju 87 variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterModification Context triple: [Jericho-Trompete siren, laterModification, often removed from later Ju 87 variants]
-
A.
leafModification
Indicates a relationship where an entity undergoes or causes a change in the structure, form, or characteristics of a leaf.
-
B.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
C.
laterInscriptionChange
Indicates a modification or addition made to an inscription at a time later than its original creation.
-
D.
amendedAt
Indicates the date and time at which an existing entity or record was modified or updated.
-
E.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:11 p.m.