Triple
T14871267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAJP |
E349748
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | CAJP |
E349748
|
NE 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: CAJP | Statement: [CAJP, shortName, CAJP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CAJP Context triple: [CAJP, shortName, CAJP]
-
A.
CAJP
chosen
CAJP is the abbreviated name for the Committee on Juridical and Political Affairs, a body that addresses legal and political issues within its organizational framework.
-
B.
CJP
CJP is the commonly used abbreviation for the Chief Justice of Pakistan, the head of the country's Supreme Court and judiciary.
-
C.
JCA
JCA is a Java EE standard that defines a pluggable architecture for integrating enterprise information systems with Java application servers.
-
D.
CACJ
CACJ is the acronym for the Central American Court of Justice, a regional judicial body that adjudicates disputes and promotes legal integration among Central American states.
-
E.
CJF
CJF is the abbreviation for Mexico’s Federal Judiciary Council, the body responsible for overseeing and administering the federal court system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded57967748190a7c05ebb74aacb7c |
completed | April 15, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe65129a588190bbad294b500f411f |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:55 a.m.