Triple
T29544251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Courts in Manipur |
E749586
|
entity |
| Predicate | procedureEmphasizes |
P143510
|
FINISHED |
| Object | conciliation and mediation |
—
|
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: conciliation and mediation | Statement: [Family Courts in Manipur, procedureEmphasizes, conciliation and mediation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: procedureEmphasizes Context triple: [Family Courts in Manipur, procedureEmphasizes, conciliation and mediation]
-
A.
procedureFeature
chosen
Indicates that a procedure possesses, involves, or is characterized by a particular feature or attribute.
-
B.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
C.
procedureArea
Indicates the physical or conceptual area in which a procedure is performed or applies.
-
D.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
E.
providesProcedure
Indicates that one entity supplies, makes available, or performs a specific procedure for another entity.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 5:06 p.m.