Triple
T9844391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIC 1917 |
E239302
|
entity |
| Predicate | abrogatedBy |
P33956
|
FINISHED |
| Object | CIC 1983 |
E754950
|
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: CIC 1983 | Statement: [CIC 1917, abrogatedBy, CIC 1983]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CIC 1983 Context triple: [CIC 1917, abrogatedBy, CIC 1983]
-
A.
CIC/83
chosen
CIC/83 is the standard abbreviation for the 1983 Code of Canon Law, the current codification of Latin-rite Catholic Church law.
-
B.
CIC
CIC is the commonly used abbreviation for the Cement Industry Committee, an organization associated with the cement sector.
-
C.
CIC
CIC is the three-letter IATA airport code assigned to Chico Municipal Airport in Chico, California.
-
D.
CIC 1917
CIC 1917 is the first comprehensive Code of Canon Law of the Catholic Church, promulgated in 1917 to systematically organize and codify ecclesiastical legislation.
-
E.
IC19
IC19 is a major Portuguese roadway linking Lisbon to the Sintra area and serving as one of the country’s busiest commuter routes.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35dc29c819080203be5b904dc9d |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e429682c8190a94339b96d4081f6 |
completed | April 5, 2026, 4:25 a.m. |
Created at: March 30, 2026, 8:33 p.m.