Triple
T3889621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rats of Tobruk |
E88026
|
entity |
| Predicate | nicknameLaterEmbracedAs |
P37280
|
FINISHED |
| Object | badge of honour |
—
|
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: badge of honour | Statement: [Rats of Tobruk, nicknameLaterEmbracedAs, badge of honour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameLaterEmbracedAs Context triple: [Rats of Tobruk, nicknameLaterEmbracedAs, badge of honour]
-
A.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
B.
isOfficialNicknameOf
chosen
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
C.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
D.
nicknameEmphasizes
Indicates that a nickname highlights or draws special attention to a particular characteristic, trait, or aspect of the entity it refers to.
-
E.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecaee7148190ada451ccfc6582ee |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.