Triple
T1626260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millbrook Commonwealth Action Programme |
E35150
|
entity |
| Predicate | adoptionDateApproximate |
P3399
|
FINISHED |
| Object | November 1995 |
—
|
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: November 1995 | Statement: [Millbrook Commonwealth Action Programme, adoptionDateApproximate, November 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptionDateApproximate Context triple: [Millbrook Commonwealth Action Programme, adoptionDateApproximate, November 1995]
-
A.
readoptedOn
Indicates the date or time at which something that was previously adopted is formally adopted again.
-
B.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
C.
officialAdoptionYear
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
-
D.
adoptedAfter
Indicates that one entity was adopted at a later time than another entity.
-
E.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.