Triple
T18631627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austronesian expansion |
E455430
|
entity |
| Predicate | approximateMadagascarSettlementDate |
P85823
|
FINISHED |
| Object | circa 500 CE |
—
|
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 500 CE | Statement: [Austronesian expansion, approximateMadagascarSettlementDate, circa 500 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateMadagascarSettlementDate Context triple: [Austronesian expansion, approximateMadagascarSettlementDate, circa 500 CE]
-
A.
relocationApproximateDate
chosen
Indicates an approximate or estimated date when a relocation or move took place.
-
B.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
E.
cityFoundedAround
Indicates that a city was established approximately at, but not exactly on, a specified time or period.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc4c5648190b771e9b080e98c15 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.