Triple
T34446877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Remo Oil Agreement |
E884252
|
entity |
| Predicate | allocatesRightsTo |
P168
|
FINISHED |
| Object | Turkish Petroleum Company |
—
|
NE NERFINISHED |
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: Turkish Petroleum Company | Statement: [San Remo Oil Agreement, allocatesRightsTo, Turkish Petroleum Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatesRightsTo Context triple: [San Remo Oil Agreement, allocatesRightsTo, Turkish Petroleum Company]
-
A.
establishesRight
Indicates that one entity creates or confers a legal or formal entitlement or privilege upon another entity.
-
B.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
C.
assignsRoleTo
Indicates that one entity designates or grants a specific role or position to another entity.
-
D.
allocationAuthority
Indicates that an entity has the power or right to decide how resources, tasks, or responsibilities are distributed among others.
-
E.
grantedTo
chosen
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7194ea5508190873287896ca6967e |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.