Triple
T850263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Lancers |
E18368
|
entity |
| Predicate | hasSquadronType |
P13144
|
FINISHED |
| Object | headquarters squadron |
—
|
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: headquarters squadron | Statement: [Royal Lancers, hasSquadronType, headquarters squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSquadronType Context triple: [Royal Lancers, hasSquadronType, headquarters squadron]
-
A.
squadronCode
Indicates the identifying code assigned to a military or aviation squadron that denotes its unit designation.
-
B.
squadron
chosen
Indicates that an entity is organized into or associated with a specific squadron as a formal operational unit.
-
C.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
D.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
E.
hasBattalion
Indicates that one entity possesses, commands, or is organizationally assigned a specific battalion.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac215194819099e6bc1b5df58fb3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.