Triple
T5187323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA-95 air defense system |
E117063
|
entity |
| Predicate | engagementRange |
P61967
|
FINISHED |
| Object | short range |
—
|
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: short range | Statement: [CA-95 air defense system, engagementRange, short range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementRange Context triple: [CA-95 air defense system, engagementRange, short range]
-
A.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
B.
engagementLevel
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
C.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
-
D.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
E.
engagementArea
Indicates the spatial region or scope within which an entity’s actions, influence, or interactions are intended to occur.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c3e9e08190848be4208b72f310 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:46 p.m.