Triple
T6741267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewisian complex basement |
E154086
|
entity |
| Predicate | minimumAgeMa |
P72691
|
FINISHED |
| Object | ca. 3000 |
—
|
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: ca. 3000 | Statement: [Lewisian complex basement, minimumAgeMa, ca. 3000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumAgeMa Context triple: [Lewisian complex basement, minimumAgeMa, ca. 3000]
-
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.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
C.
minimumRegistrationAge
Indicates the lowest age at which an entity is allowed or eligible to register for something.
-
D.
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.
-
E.
ageLimitIntroduced
Indicates that a specific age restriction or minimum/maximum age requirement has been formally established or put into effect for something.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18971e081908372cd25d52a11bd |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:10 p.m.