Triple
T29401812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JPDA Treaty |
E745662
|
entity |
| Predicate | allocatesRevenueShareToTimorLeste |
P50442
|
FINISHED |
| Object | 90 percent |
—
|
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: 90 percent | Statement: [JPDA Treaty, allocatesRevenueShareToTimorLeste, 90 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatesRevenueShareToTimorLeste Context triple: [JPDA Treaty, allocatesRevenueShareToTimorLeste, 90 percent]
-
A.
oilRevenueSharingRatio
Indicates the proportion in which oil-generated revenue is divided or shared between involved parties.
-
B.
allocatesSovereigntyTo
Indicates that an authority or framework assigns or grants sovereign power or jurisdiction over a territory, people, or domain to a specific entity.
-
C.
allocatesToCountry
chosen
Indicates that a resource, amount, or responsibility is assigned or distributed to a specific country.
-
D.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
E.
apportionedTo
Indicates that something has been divided and assigned in specific shares or portions to a particular recipient or target.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:51 p.m.