Triple
T18621412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baku oil fields |
E455157
|
entity |
| Predicate | inceptionAsRecognizedOilRegion |
P132435
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Baku oil fields, inceptionAsRecognizedOilRegion, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsRecognizedOilRegion Context triple: [Baku oil fields, inceptionAsRecognizedOilRegion, 19th century]
-
A.
hasSignificantOilReservesInRegion
Indicates that an entity possesses substantial oil reserves located within a specified geographic region.
-
B.
isPartOfOilRichRegion
Indicates that an entity is located within or belongs to a geographic area characterized by abundant oil resources.
-
C.
isOilIndustryHub
Indicates that a location serves as a central focal point for activities, infrastructure, and operations related to the oil industry.
-
D.
containsOilField
Indicates that one entity geographically includes or encompasses an oil field within its boundaries.
-
E.
areOilProducingPeople
Indicates that the people in question are involved in or associated with the production of oil.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f0146f48190a872032db6e660c6 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.