Triple
T10304772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magway Region |
E241721
|
entity |
| Predicate | hasNotableResource |
P50468
|
FINISHED |
| Object | onshore oil fields |
—
|
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: onshore oil fields | Statement: [Magway Region, hasNotableResource, onshore oil fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableResource Context triple: [Magway Region, hasNotableResource, onshore oil fields]
-
A.
hasNotableItem
chosen
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
B.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
C.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasNotableMetric
Indicates that an entity is associated with a specific metric or measurement that is considered significant or noteworthy in its context.
-
E.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:45 a.m.