Triple
T14444683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Favrile glass |
E358171
|
entity |
| Predicate | trademarkRegistered |
P54500
|
FINISHED |
| Object | 1894 |
—
|
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: 1894 | Statement: [Favrile glass, trademarkRegistered, 1894]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trademarkRegistered Context triple: [Favrile glass, trademarkRegistered, 1894]
-
A.
trademark
Indicates that one entity legally owns and uses a distinctive sign, name, or symbol to identify and distinguish its goods or services from those of others.
-
B.
visualTrademark
Indicates that one entity serves as a visual trademark or logo representing another entity.
-
C.
trademarkOwner
Indicates that one entity legally owns and holds the rights to a particular trademark associated with another entity or product.
-
D.
hostTrademark
Indicates that one entity serves as the host or platform on which another entity’s trademark is presented, displayed, or made available.
-
E.
trademarkAction
chosen
Indicates an action or legal event taken regarding a trademark, such as filing, registering, transferring, enforcing, or challenging trademark rights.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915e76f481909fe9462f964b5b1c |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.