Triple
T8263611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | family courts of Chile |
E193248
|
entity |
| Predicate | hasSupportStaff |
P81570
|
FINISHED |
| Object | court clerks |
—
|
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: court clerks | Statement: [family courts of Chile, hasSupportStaff, court clerks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportStaff Context triple: [family courts of Chile, hasSupportStaff, court clerks]
-
A.
hasAgencySupport
Indicates that an entity receives backing, assistance, or sponsorship from an agency.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasStaffedTicketOffice
Indicates that a location or facility has a ticket office that is staffed by personnel.
-
D.
hasCustomerAssistanceArea
Indicates that an entity includes or provides a designated area or facility for assisting customers.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_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. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:49 p.m.