Triple
T27534876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War I veterans |
E695069
|
entity |
| Predicate | notablyOrganized |
P201320
|
FINISHED |
| Object | Bonus Army march |
—
|
NE NERFINISHED |
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: Bonus Army march | Statement: [World War I veterans, notablyOrganized, Bonus Army march]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyOrganized Context triple: [World War I veterans, notablyOrganized, Bonus Army march]
-
A.
isOrganized
Indicates that an entity arranges, structures, or systematizes another entity or set of elements according to some order or plan.
-
B.
fullyOrganizedBy
Indicates that an event, activity, or process is completely planned, coordinated, and managed by a specified organizing entity.
-
C.
organizedWith
Indicates that entities are arranged, structured, or coordinated together as part of the same organizing scheme or effort.
-
D.
organizedSince
Indicates that an entity has been formally organized or established starting from a specified point in time.
-
E.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69ffebbcef80819099714fa9b7fda762 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 27, 2026, 1:28 p.m.