Triple
T17418663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heraldic eagle (1986–2021) |
E423550
|
entity |
| Predicate | designApprovalYear |
P51353
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [heraldic eagle (1986–2021), designApprovalYear, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designApprovalYear Context triple: [heraldic eagle (1986–2021), designApprovalYear, 1985]
-
A.
designApprovedInYear
chosen
Indicates that a particular design received formal approval in the specified year.
-
B.
designYear
Indicates the year in which something was originally designed or conceived.
-
C.
designCompletionYear
Indicates the calendar year in which the design of something was completed.
-
D.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
E.
approximateDesignYear
Indicates the estimated or inferred year in which something was designed, rather than a precisely known design year.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44234d840819096484a15d407785a |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.