Triple
T4588325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austronesian peoples |
E103422
|
entity |
| Predicate | estimatedInitialExpansionDate |
P58160
|
FINISHED |
| Object | around 3000–1500 BCE |
—
|
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: around 3000–1500 BCE | Statement: [Austronesian peoples, estimatedInitialExpansionDate, around 3000–1500 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedInitialExpansionDate Context triple: [Austronesian peoples, estimatedInitialExpansionDate, around 3000–1500 BCE]
-
A.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
B.
expansionReleaseDate
Indicates the date on which an expansion (such as an add-on or supplementary release) is officially made available.
-
C.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
D.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
-
E.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592115fc8190b1aee1d8bbaf1ee3 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.