Triple
T31047918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebec law |
E791177
|
entity |
| Predicate | hasMainCode |
P60019
|
FINISHED |
| Object | Civil Code of Quebec |
—
|
NE NERFINISHED |
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: Civil Code of Quebec | Statement: [Quebec law, hasMainCode, Civil Code of Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCode Context triple: [Quebec law, hasMainCode, Civil Code of Quebec]
-
A.
hasMainSource
chosen
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
B.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
C.
hasMainSymbol
Indicates that one entity is designated as the primary or most representative symbol associated with another entity.
-
D.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
-
E.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: April 29, 2026, 9 p.m.