Triple
T23355559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banaban people |
E593036
|
entity |
| Predicate | legalClaimOver |
P106534
|
FINISHED |
| Object | Banaba Island |
—
|
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: Banaba Island | Statement: [Banaban people, legalClaimOver, Banaba Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalClaimOver Context triple: [Banaban people, legalClaimOver, Banaba Island]
-
A.
legalClaimBy
chosen
Indicates that a specific party initiates or holds a legal claim against another party or concerning a particular matter.
-
B.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
C.
lostClaimTo
Indicates that one entity previously held a right or ownership over something but no longer retains that claim, often due to transfer, forfeiture, or invalidation.
-
D.
makesClaim
Indicates that one entity asserts, states, or puts forward a claim about another entity or about some proposition.
-
E.
legalSystemClaimed
Indicates that a particular legal system asserts authority or jurisdiction over a given entity, situation, or matter.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a176b548190bf5a08bb2585344d |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:26 p.m.