Triple
T24090610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Forces Group |
E596775
|
entity |
| Predicate | canDeployOverseas |
P8483
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Special Forces Group, canDeployOverseas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDeployOverseas Context triple: [Special Forces Group, canDeployOverseas, true]
-
A.
couldServeOverseas
chosen
Indicates that an entity has the ability or eligibility to perform service or duties in a foreign or overseas location.
-
B.
locatedInOverseasCountry
Indicates that an entity is situated in a country that is overseas relative to a given reference location or jurisdiction.
-
C.
hasOverseasPresenceIn
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
D.
canBePaidOverseas
Indicates that a payment or financial obligation is eligible to be made from or processed in a foreign country.
-
E.
overseasCountry
Indicates that one entity is a country located outside the primary or reference country associated with the other 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2e672c8190b3e4be041835cc27 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:52 p.m.