Triple
T37851602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry McKenna |
E944068
|
entity |
| Predicate | mustBeAgedAtLeast |
P156681
|
FINISHED |
| Object | 4 years |
—
|
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: 4 years | Statement: [Henry McKenna, mustBeAgedAtLeast, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeAgedAtLeast Context triple: [Henry McKenna, mustBeAgedAtLeast, 4 years]
-
A.
setsMinimumAge
Indicates that an entity establishes the lowest permissible age required for participation, access, or eligibility in relation to another entity or activity.
-
B.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
C.
minimumAgeInYears
chosen
Indicates the smallest number of years an entity must have lived or existed to meet a specified age requirement.
-
D.
ageConstraint
Indicates a restriction or condition based on the age of an entity relative to a specified threshold or range.
-
E.
ageConstraintMethod
Indicates the rule or approach used to define or enforce an age-related restriction between entities.
- 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_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.