Triple
T2881716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General of the Army |
E59410
|
entity |
| Predicate | isOftenConsidered |
P38176
|
FINISHED |
| Object | ceremonial or honorary in peacetime |
—
|
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: ceremonial or honorary in peacetime | Statement: [General of the Army, isOftenConsidered, ceremonial or honorary in peacetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenConsidered Context triple: [General of the Army, isOftenConsidered, ceremonial or honorary in peacetime]
-
A.
oftenHeldToBe
chosen
Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
-
B.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
C.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
D.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
E.
isSometimesClassifiedAs
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02aa5948190a2e0bd9168232bd5 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.