Triple
T17706533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komeito Osaka chapter |
E441445
|
entity |
| Predicate | positionOnOsakaMetropolisPlan |
P79168
|
FINISHED |
| Object | opposed |
—
|
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: opposed | Statement: [Komeito Osaka chapter, positionOnOsakaMetropolisPlan, opposed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnOsakaMetropolisPlan Context triple: [Komeito Osaka chapter, positionOnOsakaMetropolisPlan, opposed]
-
A.
positionOnHonshu
Indicates that one entity is geographically located on the island of Honshu in Japan.
-
B.
positionInShikokuPilgrimage
Indicates the specific sequential position an entity holds along the route of the Shikoku pilgrimage.
-
C.
positionInPlan
chosen
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
D.
locatedInPrefectureLevel
Indicates that one entity is geographically situated within, and administratively belongs to, a specific prefecture-level jurisdiction.
-
E.
locationOfPlanning
Indicates the place or setting where the planning activity or process occurs.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47297f7188190ba859d71e394bd4b |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.