Triple
T3079783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odaiba |
E64227
|
entity |
| Predicate | majorDevelopmentPeriod |
P22203
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Odaiba, majorDevelopmentPeriod, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDevelopmentPeriod Context triple: [Odaiba, majorDevelopmentPeriod, 1990s]
-
A.
mainDevelopmentPeriod
chosen
Indicates the primary time span during which the main development or formation of something took place.
-
B.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
C.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
D.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
E.
significantDevelopmentUnder
Indicates that one entity has undergone a major or notable development, change, or advancement under the influence, authority, or conditions provided by another entity.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a9d61081909953eb2f4ad4537e |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.