Triple
T16570079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medal of the Crimean War |
E402560
|
entity |
| Predicate | namedOnRim |
P124096
|
FINISHED |
| Object | recipient’s details engraved on rim |
—
|
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: recipient’s details engraved on rim | Statement: [Medal of the Crimean War, namedOnRim, recipient’s details engraved on rim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedOnRim Context triple: [Medal of the Crimean War, namedOnRim, recipient’s details engraved on rim]
-
A.
hasRim
Indicates that one entity possesses or is equipped with a rim as a defining part or feature.
-
B.
hasRimCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to its rim.
-
C.
ringName
Indicates that a ring is identified or referred to by a specific name.
-
D.
hasRoadAlongRim
Indicates that a road runs adjacent to and follows the contour of a rim or edge of a geographic feature.
-
E.
hasRimDiameter
Indicates that one entity has a rim whose diameter is measured by or corresponds to the value or object represented by the other entity.
- F. None of above. chosen
Provenance (4 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e359580f548190a21afd148bc22d8d |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.