Triple
T18286365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1880 Republican National Convention |
E437993
|
entity |
| Predicate | adoptedPlatformOn |
P131190
|
FINISHED |
| Object | protective tariff |
—
|
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: protective tariff | Statement: [1880 Republican National Convention, adoptedPlatformOn, protective tariff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedPlatformOn Context triple: [1880 Republican National Convention, adoptedPlatformOn, protective tariff]
-
A.
announcedPlatform
Indicates that an entity has publicly revealed or introduced a particular platform (such as a system, service, or technology).
-
B.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
C.
usedByPlatform
Indicates that something (such as a tool, component, or resource) is utilized or employed by a particular platform.
-
D.
emergedOnPlatform
Indicates that an entity became visible, active, or came into existence on a specified platform.
-
E.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fa2f308190a4744a4ed630b8d9 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.