Triple
T21412095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | courts of Tuvalu |
E528197
|
entity |
| Predicate | sometimesReliesOn |
P22819
|
FINISHED |
| Object | judges from other Commonwealth jurisdictions |
—
|
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: judges from other Commonwealth jurisdictions | Statement: [courts of Tuvalu, sometimesReliesOn, judges from other Commonwealth jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesReliesOn Context triple: [courts of Tuvalu, sometimesReliesOn, judges from other Commonwealth jurisdictions]
-
A.
reliedOn
chosen
Indicates that one entity depends on another for support, resources, or functionality.
-
B.
mayRelateTo
Indicates a possible, but not certain, relationship or association between two entities.
-
C.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
-
D.
conditionRelatesTo
Indicates that one condition is relevant, connected, or applicable to another condition or contextual factor.
-
E.
relatedRequirement
Indicates that one requirement has a defined relationship or dependency with another requirement.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d01634819089dd64fe7bc5ccbd |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:43 p.m.