Triple
T4297167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Austronesian |
E99741
|
entity |
| Predicate | hasEstimatedDating |
P877
|
FINISHED |
| Object | circa 4000–3000 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: circa 4000–3000 BCE | Statement: [Proto-Austronesian, hasEstimatedDating, circa 4000–3000 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstimatedDating Context triple: [Proto-Austronesian, hasEstimatedDating, circa 4000–3000 BCE]
-
A.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
C.
likelyDatingTo
Indicates that something probably originates from or was created in a particular time period or date range.
-
D.
likelyDatingFrom
Indicates that something is estimated or believed to originate from, or have begun in, a particular time period or date.
-
E.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509aebd48190af38f2e37f07869a |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.