Triple
T4339901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declarations (law) |
E97553
|
entity |
| Predicate | may |
P56138
|
FINISHED |
| Object | be used as interpretative tools by 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: be used as interpretative tools by courts | Statement: [Declarations (law), may, be used as interpretative tools by courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: may Context triple: [Declarations (law), may, be used as interpretative tools by courts]
-
A.
march
Indicates moving in a steady, rhythmic, and often organized or coordinated manner, typically as part of a group or formation.
-
B.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head of another entity.
-
C.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
D.
mayFile
Indicates that an entity is permitted or authorized to submit or register a formal document or application.
-
E.
among
Indicates that one or more entities are considered as part of, or in relation to, a larger group or collection of entities.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516f92588190bdf004d8020c1203 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b350d1649881908fa6556d875a8b4d |
completed | March 12, 2026, 11:48 p.m. |
Created at: March 12, 2026, 11:14 p.m.