Triple
T26581005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union shield (2010–present) |
E667075
|
entity |
| Predicate | reverseOf |
P38095
|
FINISHED |
| Object | Lincoln cent (2010–present) |
—
|
NE NERFINISHED |
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: Lincoln cent (2010–present) | Statement: [Union shield (2010–present), reverseOf, Lincoln cent (2010–present)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseOf Context triple: [Union shield (2010–present), reverseOf, Lincoln cent (2010–present)]
-
A.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
B.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
C.
alsoReveres
Indicates that one entity holds reverence or deep respect for something or someone that another entity also reveres.
-
D.
reverseMotif
Indicates that one motif is the reversed or inverted form of another motif in structure, order, or direction.
-
E.
hasReverse
chosen
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 2:03 a.m.