Triple
T8492734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comporellon |
E201011
|
entity |
| Predicate | legalSystemCharacteristic |
P25070
|
FINISHED |
| Object | strict |
—
|
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: strict | Statement: [Comporellon, legalSystemCharacteristic, strict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalSystemCharacteristic Context triple: [Comporellon, legalSystemCharacteristic, strict]
-
A.
legalSystemFeature
chosen
Indicates a characteristic, rule, or structural element that forms part of a particular legal system.
-
B.
legalSystem
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
C.
legalSystemDepictedAs
Indicates that one entity portrays, represents, or characterizes a legal system in a particular way or form.
-
D.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
-
E.
countryOfLegalSystem
Indicates the relationship between a legal system and the country in which that legal system is officially established or applied.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55cf5dc81908cad31ac53e15b46 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.