Triple
T25782959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Agreement on Peace, Security and Development on Bougainville |
E649338
|
entity |
| Predicate | continentOfSigning |
P148713
|
FINISHED |
| Object | Oceania |
—
|
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: Oceania | Statement: [Lincoln Agreement on Peace, Security and Development on Bougainville, continentOfSigning, Oceania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentOfSigning Context triple: [Lincoln Agreement on Peace, Security and Development on Bougainville, continentOfSigning, Oceania]
-
A.
continentOfSignature
chosen
Indicates the continent on which the signing of a document, agreement, or signature-related event took place.
-
B.
continentOfUse
Indicates the continent where something is primarily used or in effect.
-
C.
continentOfGoverningBody
Indicates the continent on which the governing body responsible for a given entity is located.
-
D.
countryOfSigner
Indicates that a specified country is the national affiliation or jurisdiction of the signer of a document or agreement.
-
E.
continentOfResidence
Indicates the continent on which a given entity currently resides or is based.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 5:52 a.m.