Triple
T5768094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5766 |
E127261
|
entity |
| Predicate | definesAttribute |
P45150
|
FINISHED |
| Object | LIFETIME |
—
|
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: LIFETIME | Statement: [RFC 5766, definesAttribute, LIFETIME]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAttribute Context triple: [RFC 5766, definesAttribute, LIFETIME]
-
A.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
B.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes another entity.
-
C.
definesElement
chosen
Indicates that one entity specifies or determines the nature, structure, or identity of another entity as its defining element.
-
D.
conveysAttribute
Indicates that one entity communicates, expresses, or imparts a particular attribute or quality to another entity.
-
E.
depictsAttribute
Indicates that one entity visually represents or illustrates a specific attribute or characteristic of another 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.