Triple
T18377403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mannar Island |
E446351
|
entity |
| Predicate | historicalPeriodOfPearlFishing |
P130898
|
FINISHED |
| Object | ancient times |
—
|
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: ancient times | Statement: [Mannar Island, historicalPeriodOfPearlFishing, ancient times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfPearlFishing Context triple: [Mannar Island, historicalPeriodOfPearlFishing, ancient times]
-
A.
historicalPeriodOfIntenseTrade
Indicates a time span characterized by unusually high levels of trade activity between parties or regions.
-
B.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
C.
historicallyFishedBy
Indicates that an area or body of water has been used for fishing by a particular entity or group in the past.
-
D.
historicalPeriodOfIntensiveQuarrying
Indicates the time span during which quarrying activities were especially frequent or intensive for a given site or resource.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179849d08190a3ffb9edc633d2ee |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:45 a.m.