Triple
T24529585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Poso Oil Field |
E606764
|
entity |
| Predicate | hasAPIGravity |
P156619
|
FINISHED |
| Object | low API gravity |
—
|
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: low API gravity | Statement: [Mount Poso Oil Field, hasAPIGravity, low API gravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAPIGravity Context triple: [Mount Poso Oil Field, hasAPIGravity, low API gravity]
-
A.
APIGravity
Indicates a relationship where one API exerts a dominant or central influence over others, drawing integrations or dependencies toward it like a gravitational pull.
-
B.
hasAPIs
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
-
C.
hasSpecificGravity
Indicates that one entity has a specific gravity value equal to or characteristic of another entity or reference substance.
-
D.
containsGraviton
Indicates that one entity includes or is composed of one or more gravitons.
-
E.
hasSurfaceGravity
Indicates that one entity possesses a specific gravitational acceleration at its surface, typically measured as the strength of gravity experienced at or near that surface.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:25 a.m.