Triple
T42378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Flag |
E835
|
entity |
| Predicate | adopted |
P3017
|
FINISHED |
| Object | 1801-01-01 |
—
|
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: 1801-01-01 | Statement: [Union Flag, adopted, 1801-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adopted Context triple: [Union Flag, adopted, 1801-01-01]
-
A.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
B.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
C.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
D.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24c083ad081909c1122c8fb29efdc |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24aba9a2c81909f769a8f22e30c92 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c0794c0819095509d970e05fc0f |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.