Triple
T28405275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napoleonic memorabilia |
E719509
|
entity |
| Predicate | hasTypicalItem |
P101738
|
FINISHED |
| Object | military uniforms from the Napoleonic era |
—
|
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 uniforms from the Napoleonic era | Statement: [Napoleonic memorabilia, hasTypicalItem, military uniforms from the Napoleonic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalItem Context triple: [Napoleonic memorabilia, hasTypicalItem, military uniforms from the Napoleonic era]
-
A.
typicalItem
chosen
Indicates that an item is a representative or characteristic example of a broader category, class, or set.
-
B.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
C.
hasTypicalCut
Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
-
D.
hasTypicalBody
Indicates that an entity possesses the standard or characteristic physical form commonly associated with its kind or category.
-
E.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 28, 2026, 1:23 a.m.