Triple
T24812167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-6 Gainful |
E620818
|
entity |
| Predicate | typicalEngagementRange |
P61967
|
FINISHED |
| Object | up to about 24 km |
—
|
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: up to about 24 km | Statement: [SA-6 Gainful, typicalEngagementRange, up to about 24 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEngagementRange Context triple: [SA-6 Gainful, typicalEngagementRange, up to about 24 km]
-
A.
engagementRange
chosen
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
typicalParticipation
Indicates that an entity commonly or characteristically takes part in a particular activity, event, or process.
-
D.
typicalAgeRangeOfPlayers
Indicates the usual age range of people who typically play or participate in something.
-
E.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 18, 2026, 4:50 a.m.