Triple
T12276707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Customary Courts (Nigeria) |
E292606
|
entity |
| Predicate | proceduralStyle |
P104190
|
FINISHED |
| Object | less formal than higher courts |
—
|
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: less formal than higher courts | Statement: [Customary Courts (Nigeria), proceduralStyle, less formal than higher courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralStyle Context triple: [Customary Courts (Nigeria), proceduralStyle, less formal than higher courts]
-
A.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
B.
developmentStyle
Indicates the manner or approach in which something is developed, such as the methodology, process, or style guiding its creation or evolution.
-
C.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
D.
proceduralRequirement
Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
-
E.
protocolStyle
Indicates the manner or format in which a protocol or communication procedure is structured or expressed.
- F. None of above. chosen
Provenance (4 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d93805cee08190a532ebcf5908e617 |
completed | April 10, 2026, 5:48 p.m. |
Created at: April 8, 2026, 9:52 p.m.