Triple
T10895179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuruvungna Springs |
E257289
|
entity |
| Predicate | timeDepthOfUse |
P63523
|
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: [Kuruvungna Springs, timeDepthOfUse, pre-colonial era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDepthOfUse Context triple: [Kuruvungna Springs, timeDepthOfUse, pre-colonial era]
-
A.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
B.
timeDepthOfLandUse
chosen
Indicates the duration or historical depth over which a particular land use has been present or practiced in a given area.
-
C.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
timeBetweenCensusAndUse
Indicates the length of time that passes between when a census is conducted and when its data is used for a particular purpose.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0153408190bcba2d9b03d78804 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.