Triple
T36391869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | commercial courts |
E896348
|
entity |
| Predicate | mayEncourage |
P836
|
FINISHED |
| Object | settlement of disputes |
—
|
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: settlement of disputes | Statement: [commercial courts, mayEncourage, settlement of disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayEncourage Context triple: [commercial courts, mayEncourage, settlement of disputes]
-
A.
encourages
chosen
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
B.
mayPromote
Indicates that one entity has the authority or permission to advance another entity to a higher rank, position, or status.
-
C.
mayEngageIn
Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with another entity.
-
D.
depictedAsEncouraging
Indicates that one entity is portrayed or represented as giving support, confidence, or motivation to another entity.
-
E.
mayEnact
Indicates that an entity has the authority or permission to establish, implement, or put into effect a rule, policy, or action.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.