Triple
T26650199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereignty over Pedra Branca case |
E669027
|
entity |
| Predicate | applicationFiledOn |
P180125
|
FINISHED |
| Object | 2003-07-24 |
—
|
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: 2003-07-24 | Statement: [Sovereignty over Pedra Branca case, applicationFiledOn, 2003-07-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationFiledOn Context triple: [Sovereignty over Pedra Branca case, applicationFiledOn, 2003-07-24]
-
A.
inventionApplication
Indicates that an entity has submitted or is associated with an application for an invention, typically for legal or patent-related purposes.
-
B.
appliedFor
Indicates that an entity has submitted a request or application to another entity for a position, service, benefit, or opportunity.
-
C.
petitionFiledBy
Indicates that a formal petition has been submitted or initiated by a particular party or entity.
-
D.
applicationStatus
Indicates the current state or outcome of an application within its processing lifecycle.
-
E.
onlineApplication
Indicates that an application or request is submitted, processed, or managed through an online or web-based system.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 27, 2026, 2:32 a.m.