Triple
T32307726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle "E" |
E825411
|
entity |
| Predicate | wearableInsigniaAuthorized |
P28027
|
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: [Battle "E", wearableInsigniaAuthorized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearableInsigniaAuthorized Context triple: [Battle "E", wearableInsigniaAuthorized, true]
-
A.
individualWearAuthorized
Indicates that an individual is wearing an item or equipment for which they have proper authorization.
-
B.
wearAuthorizedFor
Indicates that an entity is permitted or authorized to wear a specified item (such as clothing, equipment, or insignia).
-
C.
wearerEntitlement
chosen
Indicates that an entity has the right or authorization to wear a particular item (such as clothing, equipment, or an accessory).
-
D.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
E.
wearAuthorizedBy
Indicates that one entity’s wearing or use of an item (such as clothing, uniform, or equipment) is permitted or approved by another 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd8835588190b562ff2832f98acf |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:45 a.m.