Triple
T34521435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy E Ribbon |
E886288
|
entity |
| Predicate | competitionBasis |
P72312
|
FINISHED |
| Object | annual or periodic battle efficiency competition |
—
|
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: annual or periodic battle efficiency competition | Statement: [Navy E Ribbon, competitionBasis, annual or periodic battle efficiency competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionBasis Context triple: [Navy E Ribbon, competitionBasis, annual or periodic battle efficiency competition]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionElement
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
C.
competitionSystem
chosen
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
-
D.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
E.
competitionSurface
Indicates the type of surface or medium on which a competition or contest takes place.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 2:02 a.m.