Triple
T21796519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Bay Plan |
E538107
|
entity |
| Predicate | hasPresentationYear |
P35430
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Tokyo Bay Plan, hasPresentationYear, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresentationYear Context triple: [Tokyo Bay Plan, hasPresentationYear, 1960]
-
A.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
-
B.
demonstrationYear
chosen
Indicates the year in which a demonstration, display, or public showing of something took place.
-
C.
hasTypeOfYear
Indicates that a given year is classified as belonging to a specific type or category of year (e.g., fiscal, academic, leap).
-
D.
yearOfPerformance
Indicates the specific calendar year in which a performance, event, or action took place.
-
E.
compilationYear
Indicates the year in which a work, collection, or set of materials was compiled or assembled into its final form.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0622502188190998638317f232334 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.