Triple
T2750764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Napoleon |
E60979
|
entity |
| Predicate | appliedDuringRole |
P41633
|
FINISHED |
| Object | General-in-Chief of the Union armies |
—
|
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-in-Chief of the Union armies | Statement: [Young Napoleon, appliedDuringRole, General-in-Chief of the Union armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedDuringRole Context triple: [Young Napoleon, appliedDuringRole, General-in-Chief of the Union armies]
-
A.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
B.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
C.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
D.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
- F. None of above. chosen
Provenance (4 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6b6f0c8190901ab032dfb21e37 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd91497ec8190927e91ad33549eda |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:56 p.m.