Triple
T18965554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Ensign of Canada |
E464028
|
entity |
| Predicate | adoptedDeFacto |
P133972
|
FINISHED |
| Object | circa 1868 |
—
|
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: circa 1868 | Statement: [Red Ensign of Canada, adoptedDeFacto, circa 1868]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedDeFacto Context triple: [Red Ensign of Canada, adoptedDeFacto, circa 1868]
-
A.
readoptedDeFacto
Indicates that an entity has been taken back or resumed in practice (though not necessarily through formal or legal means) after having been previously discontinued or relinquished.
-
B.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
-
C.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
D.
officiallyAdopted
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
-
E.
adoptadoEl
Indicates that one entity has been adopted by another entity (e.g., a person, family, or organization).
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d663948190b496fbd2e69c7f43 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon