Triple
T35455796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval General Service Medal |
E1024768
|
entity |
| Predicate | notableClasp |
P206992
|
FINISHED |
| Object | Trafalgar |
E11152
|
NE 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: Trafalgar | Statement: [Naval General Service Medal, notableClasp, Trafalgar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClasp Context triple: [Naval General Service Medal, notableClasp, Trafalgar]
-
A.
notableClass
Indicates that an entity belongs to a particularly important, distinguished, or otherwise noteworthy class or category within a given classification system.
-
B.
notableTie
Indicates a significant connection or association between entities that is noteworthy or distinguished in some context.
-
C.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
D.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- F. None of above. chosen
Provenance (5 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836cdeb248190a797d01ebe6b3a7d |
completed | June 21, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.