Triple
T38555072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | national railway network of Japan |
E925220
|
entity |
| Predicate | servesMajorCity |
P3936
|
FINISHED |
| Object | Tokyo |
—
|
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: Tokyo | Statement: [national railway network of Japan, servesMajorCity, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMajorCity Context triple: [national railway network of Japan, servesMajorCity, Tokyo]
-
A.
cityOfMajorPresence
Indicates that an entity has a significant or primary operational, demographic, or functional presence in the specified city.
-
B.
isMajorCityIn
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
C.
servedCity
chosen
Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
-
D.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
E.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00ab25c5b48190ad07ff508392ef56 |
completed | May 10, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_6a00a8a5cfc48190bbe97fb2bbd1b947 |
completed | May 10, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:32 p.m.