Triple
T25887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Union Flag |
E517
|
entity |
| Predicate | legalSuccessorFlag |
P78
|
FINISHED |
| Object | Flag Resolution of 1777 flag |
—
|
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: Flag Resolution of 1777 flag | Statement: [Grand Union Flag, legalSuccessorFlag, Flag Resolution of 1777 flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalSuccessorFlag Context triple: [Grand Union Flag, legalSuccessorFlag, Flag Resolution of 1777 flag]
-
A.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
B.
successionDefinedBy
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
-
C.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
E.
legalRecognition
Indicates that an authority formally acknowledges the validity, status, or rights associated with an entity, relationship, or action under the law.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246d794448190bb2844fcd0538eaa |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a24657635881908f3415bc1bdfa1b5 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.