Triple
T6727348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Tokyo |
E153549
|
entity |
| Predicate | UNLocode |
P1800
|
FINISHED |
| Object |
JPTYO
JPTYO is the UN/LOCODE identifier for the Port of Tokyo, a major international seaport serving Japan’s capital city.
|
E613164
|
NE FINISHED |
How this triple was built (4 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: JPTYO | Statement: [Port of Tokyo, UNLocode, JPTYO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JPTYO Context triple: [Port of Tokyo, UNLocode, JPTYO]
-
A.
JPO
JPO is an acronym commonly used for the Joint Program Office, a centralized organization that manages and oversees major joint military acquisition programs.
-
B.
YPJ
YPJ is an all-female Kurdish militia in northern Syria known for its prominent role in the fight against ISIS and its advocacy of gender equality.
-
C.
JPITM
JPITM is the UN/LOCODE identifier for Osaka International Airport, a major domestic airport serving the Osaka metropolitan area in Japan.
-
D.
JPVT
JPVT is the standard abbreviation for the ASME Journal of Pressure Vessel Technology, a peer-reviewed journal focusing on research and developments in pressure vessel and piping engineering.
-
E.
Tokyo Kyojin
Tokyo Kyojin is an alternate name for the Yomiuri Giants, one of Japan’s most historic and successful professional baseball teams based in Tokyo.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: JPTYO Triple: [Port of Tokyo, UNLocode, JPTYO]
Generated description
JPTYO is the UN/LOCODE identifier for the Port of Tokyo, a major international seaport serving Japan’s capital city.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: JPTYO Target entity description: JPTYO is the UN/LOCODE identifier for the Port of Tokyo, a major international seaport serving Japan’s capital city.
-
A.
JPO
JPO is an acronym commonly used for the Joint Program Office, a centralized organization that manages and oversees major joint military acquisition programs.
-
B.
YPJ
YPJ is an all-female Kurdish militia in northern Syria known for its prominent role in the fight against ISIS and its advocacy of gender equality.
-
C.
JPITM
JPITM is the UN/LOCODE identifier for Osaka International Airport, a major domestic airport serving the Osaka metropolitan area in Japan.
-
D.
JPVT
JPVT is the standard abbreviation for the ASME Journal of Pressure Vessel Technology, a peer-reviewed journal focusing on research and developments in pressure vessel and piping engineering.
-
E.
Tokyo Kyojin
Tokyo Kyojin is an alternate name for the Yomiuri Giants, one of Japan’s most historic and successful professional baseball teams based in Tokyo.
- F. None of above. chosen
Provenance (5 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d152a4908190a041f2049240e7ca |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c700a645dc8190af04b643b46c3e5d |
completed | March 27, 2026, 10:11 p.m. |
| NEDg | Description generation | batch_69c70386196c81909d46894f783ef87a |
completed | March 27, 2026, 10:24 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c7045cda0481908982c7c7e8dc11e5 |
completed | March 27, 2026, 10:27 p.m. |
Created at: March 27, 2026, 2:08 p.m.