Triple
T14685298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reveille (bugle call) |
E344893
|
entity |
| Predicate | hasTypicalContext |
P39989
|
FINISHED |
| Object | military tradition |
—
|
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: military tradition | Statement: [Reveille (bugle call), hasTypicalContext, military tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalContext Context triple: [Reveille (bugle call), hasTypicalContext, military tradition]
-
A.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
-
B.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
C.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
-
D.
typicalAppearanceContext
chosen
Indicates the usual situation, setting, or context in which an entity most commonly appears or is typically encountered.
-
E.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56bdb8081909ff86440ba20fb1f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.