Triple
T2715761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayman Islands Constitution Order 2009 |
E59962
|
entity |
| Predicate | SInumber |
P37553
|
FINISHED |
| Object | 2009 No. 1379 |
—
|
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: 2009 No. 1379 | Statement: [Cayman Islands Constitution Order 2009, SInumber, 2009 No. 1379]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SInumber Context triple: [Cayman Islands Constitution Order 2009, SInumber, 2009 No. 1379]
-
A.
SSNumber
Indicates that an entity has a specific Social Security Number assigned to it.
-
B.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
C.
MMSINumber
Indicates a relationship where a mobile subscriber is associated with a specific Mobile Station International ISDN Number (MSISDN) used to identify their phone line in a mobile network.
-
D.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
E.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda94d3288190bd60bc886e2106c7 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.