Triple
T27793802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ga Traditional Area |
E701150
|
entity |
| Predicate | historicallyInhabitedSince |
P22541
|
FINISHED |
| Object | pre-colonial era |
—
|
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: pre-colonial era | Statement: [Ga Traditional Area, historicallyInhabitedSince, pre-colonial era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyInhabitedSince Context triple: [Ga Traditional Area, historicallyInhabitedSince, pre-colonial era]
-
A.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
inhabitedSince
chosen
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
C.
earliestSettlementEstimate
Indicates the earliest estimated point in time when a particular settlement or habitation is believed to have begun.
-
D.
inhabitedDuring
Indicates that an entity lived in or occupied a place during a specified time period.
-
E.
wasPopulatedPlaceUntil
Indicates that a location functioned as a populated place up to a specified point in time, after which it no longer held that status.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 27, 2026, 5:29 p.m.