Triple
T26537936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJOA |
E671300
|
entity |
| Predicate | airportPrefecture |
P10426
|
FINISHED |
| Object | Hiroshima Prefecture |
—
|
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: Hiroshima Prefecture | Statement: [RJOA, airportPrefecture, Hiroshima Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportPrefecture Context triple: [RJOA, airportPrefecture, Hiroshima Prefecture]
-
A.
airlineBasePrefecture
Indicates the prefecture in which an airline has its primary base of operations.
-
B.
hostPrefecture
chosen
Indicates the prefecture that serves as the host location for an event, activity, or entity.
-
C.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
-
D.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
E.
destinationPrefecture
Indicates the prefecture that serves as the destination location associated with an entity or event.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 1:39 a.m.