Triple
T9849606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Johns |
E239430
|
entity |
| Predicate | forceComponent |
P52099
|
FINISHED |
| Object | Primary Reserve |
—
|
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: Primary Reserve | Statement: [The Johns, forceComponent, Primary Reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceComponent Context triple: [The Johns, forceComponent, Primary Reserve]
-
A.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
B.
forceComponentCreated
Indicates that a force-related component has been instantiated or newly created within a system or context.
-
C.
forceElement
chosen
Indicates a physical or conceptual force acting upon, influencing, or constraining another element within a system or interaction.
-
D.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
E.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb372efc88190a801b2d7384445d7 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.