Triple
T23502674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ledaig |
E571893
|
entity |
| Predicate | ageStatementAvailable |
P141254
|
FINISHED |
| Object | 10-year-old |
—
|
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: 10-year-old | Statement: [Ledaig, ageStatementAvailable, 10-year-old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageStatementAvailable Context triple: [Ledaig, ageStatementAvailable, 10-year-old]
-
A.
ageStatement
chosen
Indicates that a statement expresses or asserts the age of an entity in terms of time lived or existed.
-
B.
ageStatementVariants
Indicates alternative phrasings or formulations used to express the same age-related statement or fact.
-
C.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
D.
canAgeFor
Indicates that one entity is capable of undergoing an aging or maturation process for the benefit, use, or context of another entity.
-
E.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a8fe1e3081908c4a9df4e137b9b3 |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:06 p.m.