Triple
T37851635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry McKenna |
E944068
|
entity |
| Predicate | isLegallyRequiredToBeMadeFromAtLeast |
P26873
|
FINISHED |
| Object | 51% corn |
—
|
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: 51% corn | Statement: [Henry McKenna, isLegallyRequiredToBeMadeFromAtLeast, 51% corn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegallyRequiredToBeMadeFromAtLeast Context triple: [Henry McKenna, isLegallyRequiredToBeMadeFromAtLeast, 51% corn]
-
A.
isMandatoryInSomeJurisdictions
chosen
Indicates that the subject is legally required or compulsory in at least one jurisdiction or legal authority.
-
B.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
C.
isObligatory
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
-
D.
isMandatoryFor
Indicates that something is required or compulsory for another thing to occur, be valid, or be completed.
-
E.
legalRequirement
Indicates that one entity is obligated by law to perform, provide, or comply with something in relation to another entity or situation.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.