Triple
T32136354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harima Province |
E820771
|
entity |
| Predicate | todayPartlyCorrespondsTo |
P25442
|
FINISHED |
| Object | Himeji City |
—
|
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: Himeji City | Statement: [Harima Province, todayPartlyCorrespondsTo, Himeji City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: todayPartlyCorrespondsTo Context triple: [Harima Province, todayPartlyCorrespondsTo, Himeji City]
-
A.
todayIn
Indicates that an entity or event occurs, is valid, or is taking place on the current calendar day.
-
B.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
-
C.
partiallyCorrespondsTo
chosen
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
D.
presentDayRemains
Indicates that something from the past still exists or has surviving traces in the present day.
-
E.
knownTodayAs
Indicates that an entity is currently referred to or recognized by a particular name or designation in the present time.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9a9bc4c8190a88918fc4f91136a |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.