Triple
T28517750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORANGE LINER |
E721667
|
entity |
| Predicate | callSignOwnerHeadquarters |
P165452
|
FINISHED |
| Object | Narita, Chiba Prefecture, Japan |
—
|
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: Narita, Chiba Prefecture, Japan | Statement: [ORANGE LINER, callSignOwnerHeadquarters, Narita, Chiba Prefecture, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignOwnerHeadquarters Context triple: [ORANGE LINER, callSignOwnerHeadquarters, Narita, Chiba Prefecture, Japan]
-
A.
callSignStation
Indicates that a particular call sign is assigned to or used by a specific station.
-
B.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific entity.
-
C.
callSignAssignmentAuthority
Indicates the authority or entity responsible for assigning call signs to other entities.
-
D.
callSignForOffice
Indicates that a particular call sign is assigned to or used for a specific office or official position.
-
E.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
- F. None of above. chosen
Provenance (4 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 3:18 a.m.