Triple
T36230379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11th Cavalry Reconnaissance Squadron (Mechanized) |
E891224
|
entity |
| Predicate | typeOfReconnaissance |
P203899
|
FINISHED |
| Object | tactical reconnaissance |
—
|
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: tactical reconnaissance | Statement: [11th Cavalry Reconnaissance Squadron (Mechanized), typeOfReconnaissance, tactical reconnaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfReconnaissance Context triple: [11th Cavalry Reconnaissance Squadron (Mechanized), typeOfReconnaissance, tactical reconnaissance]
-
A.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
C.
typeOfExplorationEquipment
Indicates that one entity is a specific kind or category of exploration equipment used for investigative or exploratory activities.
-
D.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
E.
methodOfInvasion
Indicates the specific way or technique by which an invasion is carried out.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
| PDg | Predicate description generation | batch_6a02480580b481909838e544d0ebfd17 |
completed | May 11, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:09 p.m.