Triple
T27555319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchell v. Helms |
E695619
|
entity |
| Predicate | hasAidForm |
P163500
|
FINISHED |
| Object | loans of instructional equipment |
—
|
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: loans of instructional equipment | Statement: [Mitchell v. Helms, hasAidForm, loans of instructional equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAidForm Context triple: [Mitchell v. Helms, hasAidForm, loans of instructional equipment]
-
A.
hasAidForm
chosen
Indicates that one entity provides or is associated with a particular form or type of aid related to another entity.
-
B.
hasAidProgram
Indicates that one entity provides or maintains an aid or assistance program for another entity or group.
-
C.
conditionForAid
Indicates that one entity constitutes a requirement or qualifying circumstance that must be met for another entity to receive aid or assistance.
-
D.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
E.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 1:36 p.m.