Triple
T1553575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope |
E33148
|
entity |
| Predicate | appearsWithSymbol |
P30273
|
FINISHED |
| Object | anchor on the Rhode Island state seal |
—
|
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: anchor on the Rhode Island state seal | Statement: [Hope, appearsWithSymbol, anchor on the Rhode Island state seal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsWithSymbol Context triple: [Hope, appearsWithSymbol, anchor on the Rhode Island state seal]
-
A.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
B.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
C.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
D.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
E.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a9407aa20881909e747f247ccec642 |
completed | March 5, 2026, 8:36 a.m. |
Created at: March 4, 2026, 7:27 p.m.