Triple
T24116702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Party |
E597532
|
entity |
| Predicate | adoptedPlatform |
P138997
|
FINISHED |
| Object | Omaha Platform |
—
|
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: Omaha Platform | Statement: [People's Party, adoptedPlatform, Omaha Platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedPlatform Context triple: [People's Party, adoptedPlatform, Omaha Platform]
-
A.
adoptedPlatformOn
Indicates that an entity began using or officially adopted a particular platform on a specific date or point in time.
-
B.
platformAdopted
chosen
Indicates that an entity has begun using or officially implemented a particular platform.
-
C.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
D.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
E.
adoptedFrameworkType
Indicates that one entity has chosen and is using a particular framework type as its adopted standard or approach.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dedf824081908de34db4ced62c13 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:04 p.m.