Triple
T27857354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman auxiliary units |
E704123
|
entity |
| Predicate | afterService |
P167792
|
FINISHED |
| Object | veteran communities in provinces |
—
|
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: veteran communities in provinces | Statement: [Roman auxiliary units, afterService, veteran communities in provinces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterService Context triple: [Roman auxiliary units, afterService, veteran communities in provinces]
-
A.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
B.
afterAD
Indicates that one event, action, or state occurs later in time than another, serving as its temporal successor.
-
C.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
D.
afterAWorkBy
Indicates that one work is created subsequent to and based on, inspired by, or derived from another existing work.
-
E.
afterAcquisitionBy
Indicates that something occurs or holds true following the acquisition of one entity by another.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 6:15 p.m.