Triple
T8263605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | family courts of Chile |
E193248
|
entity |
| Predicate | usesProcedureType |
P67337
|
FINISHED |
| Object | oral proceedings |
—
|
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: oral proceedings | Statement: [family courts of Chile, usesProcedureType, oral proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProcedureType Context triple: [family courts of Chile, usesProcedureType, oral proceedings]
-
A.
usedProceduralLanguage
Indicates that an entity carried out an action or implemented something by means of a procedural programming language.
-
B.
typeOfProcedureHandled
chosen
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
C.
hasProceduralRole
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
-
D.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
E.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793991b481908ad7221405e88ab7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.