Triple
T366965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half Eagle |
E7981
|
entity |
| Predicate | compositionChanged |
P11662
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Half Eagle, compositionChanged, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionChanged Context triple: [Half Eagle, compositionChanged, yes]
-
A.
compositionChamber
Indicates a relationship where a chamber or enclosed space is used as the setting or environment in which a composition (such as a musical, chemical, or artistic work) is created or formed.
-
B.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
D.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
E.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.