Triple
T14144639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel of the Battlefield |
E350512
|
entity |
| Predicate | eraOfReferentActivity |
P54160
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Angel of the Battlefield, eraOfReferentActivity, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfReferentActivity Context triple: [Angel of the Battlefield, eraOfReferentActivity, 19th century]
-
A.
eraOfBoundaryRole
Indicates the historical period or era during which a particular boundary role is defined, active, or relevant.
-
B.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
C.
eraManagedIn
Indicates that an entity (such as a project, resource, or process) was administered, controlled, or overseen during a specific time period or era.
-
D.
eraOfHonouredPersonActivity
chosen
Indicates the historical period or era during which the honoured person carried out their notable activities.
-
E.
refersToEventType
Indicates that one entity references or is associated with a specific type or category of event.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61214de081909a5186ff11336f97 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:53 a.m.