Triple
T27860005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Cyr cadet sword |
E704197
|
entity |
| Predicate | wearerRank |
P145214
|
FINISHED |
| Object | officer cadet |
—
|
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: officer cadet | Statement: [Saint-Cyr cadet sword, wearerRank, officer cadet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerRank Context triple: [Saint-Cyr cadet sword, wearerRank, officer cadet]
-
A.
wearerRankCategory
Indicates the classification of the wearer's rank into a broader rank category (e.g., junior, senior, officer, etc.) within a ranking system.
-
B.
wearerRankRange
chosen
Indicates the range of ranks that an individual must fall within in order to be permitted or intended to wear a specified item.
-
C.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
D.
wearerTitle
Indicates that a specified title or designation is held by the wearer of an item or garment.
-
E.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6394220d88190a9d7d5f5ebcf5e4f |
completed | May 2, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:17 p.m.