Triple
T35962086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haneda |
E1040025
|
entity |
| Predicate | hasAlternativeSpellingSystem |
P457
|
FINISHED |
| Object | Hepburn romanization |
—
|
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: Hepburn romanization | Statement: [Haneda, hasAlternativeSpellingSystem, Hepburn romanization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeSpellingSystem Context triple: [Haneda, hasAlternativeSpellingSystem, Hepburn romanization]
-
A.
usesPhoneticSystem
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
B.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
C.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
D.
hasDistinctOrthographyFrom
Indicates that two written forms are orthographically different from each other, even if they may represent the same or related linguistic content.
-
E.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.