Triple
T32307706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle "E" |
E825411
|
entity |
| Predicate | isUnitLevelAward |
P18108
|
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", isUnitLevelAward, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnitLevelAward Context triple: [Battle "E", isUnitLevelAward, true]
-
A.
hasUnitLevel
Indicates that something is associated with, measured at, or applicable to a specific unit level within a larger hierarchy or scale.
-
B.
hasAwardLevel
chosen
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
-
C.
hasAwardUnit
Indicates that an award is associated with, measured in, or granted in terms of a specific unit (such as a quantity, category, or subdivision).
-
D.
isAward
Indicates that one entity functions as an award or prize that is given or conferred to another entity.
-
E.
isPlayerAward
Indicates that an award is designated specifically for a player, representing a recognition or honor given to an individual participant.
- 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.