Triple
T28498848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metropolitan Routes |
E721178
|
entity |
| Predicate | hasSignCode |
P179211
|
FINISHED |
| Object | prefectural road route marker of Tokyo |
—
|
LITERAL FINISHED |
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: prefectural road route marker of Tokyo | Statement: [Tokyo Metropolitan Routes, hasSignCode, prefectural road route marker of Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignCode Context triple: [Tokyo Metropolitan Routes, hasSignCode, prefectural road route marker of Tokyo]
-
A.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
C.
haveSigned
Indicates that an entity has completed and formally agreed to a document, contract, or agreement by signing it.
-
D.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
E.
hasSignatureUser
Indicates that a particular user is designated as the signer or signature owner associated with an entity or record.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 28, 2026, 3:05 a.m.