Triple
T2821977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMNZS Achilles |
E54829
|
entity |
| Predicate | fame |
P27257
|
FINISHED |
| Object | early Allied victory publicity in World War II |
—
|
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: early Allied victory publicity in World War II | Statement: [HMNZS Achilles, fame, early Allied victory publicity in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fame Context triple: [HMNZS Achilles, fame, early Allied victory publicity in World War II]
-
A.
fameStatus
chosen
Indicates the level or state of public recognition or renown associated with an entity.
-
B.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
C.
popularName
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
D.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
E.
honour
Indicates showing respect, admiration, or recognition toward someone or something, often through actions, words, or ceremonial acknowledgment.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.