Triple
T10632036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 601st Special Forces Group |
E250479
|
entity |
| Predicate | isLandForcesUnit |
P21175
|
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: [601st Special Forces Group, isLandForcesUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLandForcesUnit Context triple: [601st Special Forces Group, isLandForcesUnit, true]
-
A.
isRegularArmyUnit
chosen
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
B.
isCombatSupportUnit
Indicates that the unit’s primary role is to provide operational or logistical support to combat forces rather than engage directly in frontline fighting.
-
C.
isInLand
Indicates that one entity is located within the geographical boundaries of a land area or territory of another entity.
-
D.
landedForce
Indicates that a force or group has arrived and come ashore at a location, typically by landing from the air or sea.
-
E.
isVolunteerForce
Indicates that a group or force is composed of individuals who serve voluntarily rather than by conscription or obligation.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df94dc1c8190b6347eaf35a5acc2 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:01 p.m.