Triple
T17650556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greatest of All Leathernecks |
E429477
|
entity |
| Predicate | honorificForRank |
P54566
|
FINISHED |
| Object | General |
—
|
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: General | Statement: [The Greatest of All Leathernecks, honorificForRank, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificForRank Context triple: [The Greatest of All Leathernecks, honorificForRank, General]
-
A.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
B.
honorificOrder
Indicates the relative ranking or sequence of entities according to a system of honorifics or formal precedence.
-
C.
honorificNameOf
chosen
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
D.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
E.
honorificLevel
Indicates the level of formality or respect expressed toward an entity, typically reflected in language or titles used when addressing or referring to them.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3c7da48190b38558bc66637687 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.