Triple
T20985888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana family courts |
E516889
|
entity |
| Predicate | canIssueOrderType |
P9835
|
FINISHED |
| Object | custody orders |
—
|
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: custody orders | Statement: [Louisiana family courts, canIssueOrderType, custody orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIssueOrderType Context triple: [Louisiana family courts, canIssueOrderType, custody orders]
-
A.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
B.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
C.
orderTypesSupported
chosen
Indicates that a system or entity supports specific types or categories of orders that can be placed or processed.
-
D.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
E.
canOrderNewTrial
Indicates that an authority (typically a court or judge) has the legal power to initiate or grant a new trial in a case.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe31cec8190a1007414148b8abe |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.