Triple
T13393451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Lama |
E319631
|
entity |
| Predicate | ageTrait |
P61009
|
FINISHED |
| Object | extremely 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: extremely old | Statement: [High Lama, ageTrait, extremely old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageTrait Context triple: [High Lama, ageTrait, extremely old]
-
A.
ageRecord
Indicates that there exists a record specifying the age of an entity at a particular time or in a particular context.
-
B.
ageDetail
chosen
Indicates a detailed specification of an entity’s age, such as exact value, range, or related age attributes.
-
C.
ageModel
Indicates a relationship where one entity specifies or provides the age of another entity, typically in terms of a particular age value or age-related classification.
-
D.
riftAge
Indicates the age or time since formation of a geological rift or rift-related feature.
-
E.
agePattern
Indicates a relationship where entities share or follow a specific configuration, distribution, or rule regarding their ages.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d74e5881909828854bba7d9a87 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.