Triple
T32278702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oruanui ignimbrite |
E824629
|
entity |
| Predicate | ageConstraintMethod |
P173916
|
FINISHED |
| Object | radiocarbon dating of associated deposits |
—
|
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: radiocarbon dating of associated deposits | Statement: [Oruanui ignimbrite, ageConstraintMethod, radiocarbon dating of associated deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageConstraintMethod Context triple: [Oruanui ignimbrite, ageConstraintMethod, radiocarbon dating of associated deposits]
-
A.
ageConstraint
Indicates a restriction or condition based on the age of an entity relative to a specified threshold or range.
-
B.
ageLimitException
Indicates that a specified age restriction does not apply or is waived under certain conditions.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
ageLimitYears
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
E.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc6cf58819092e006e741a628bb |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:43 a.m.