Triple
T1360923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okinawan Japanese |
E29095
|
entity |
| Predicate | periodOfDevelopment |
P24285
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Okinawan Japanese, periodOfDevelopment, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfDevelopment Context triple: [Okinawan Japanese, periodOfDevelopment, 20th century]
-
A.
developmentalFor
Indicates that one entity serves as a developmental precursor, stage, or necessary condition for the emergence or maturation of another entity.
-
B.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
C.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
D.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
E.
hadGrowthPeriod
chosen
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b156b081909c99ada70a969fc0 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.