Triple
T11617752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fennec |
E275552
|
entity |
| Predicate | modificationPurpose |
P5019
|
FINISHED |
| Object | improved combat capability |
—
|
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: improved combat capability | Statement: [Fennec, modificationPurpose, improved combat capability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modificationPurpose Context triple: [Fennec, modificationPurpose, improved combat capability]
-
A.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
B.
modificationOrigin
Indicates the source or cause from which a particular change or modification to an entity originates.
-
C.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
D.
changeReason
chosen
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a047758081908191c1d564409d9a |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.