Triple
T32361215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-25 Sickle |
E826866
|
entity |
| Predicate | roadMobilityAdvantage |
P174186
|
FINISHED |
| Object | increased survivability |
—
|
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: increased survivability | Statement: [SS-25 Sickle, roadMobilityAdvantage, increased survivability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadMobilityAdvantage Context triple: [SS-25 Sickle, roadMobilityAdvantage, increased survivability]
-
A.
mobilityEmphasis
Indicates a focus on or prioritization of movement, travel, or physical relocation within the relationship or action.
-
B.
mobilitySegment
Indicates a distinct portion or phase within a broader movement or travel activity, treated as a separate unit of mobility.
-
C.
roadwayCarries
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
-
D.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
E.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be97650c8190b4facad50682b451 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:49 a.m.