Triple
T33186431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6797 |
E849481
|
entity |
| Predicate | definesDirective |
P196636
|
FINISHED |
| Object | max-age |
—
|
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: max-age | Statement: [RFC 6797, definesDirective, max-age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesDirective Context triple: [RFC 6797, definesDirective, max-age]
-
A.
definesMacro
Indicates that one entity specifies or declares a macro that can be used or expanded by another entity.
-
B.
definesSyntax
Indicates that one entity specifies or determines the formal structure, rules, or grammar by which another entity is expressed or interpreted.
-
C.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
D.
interpretsDirectiveAs
Indicates that an agent understands or construes a given directive in a particular way or with a specific meaning.
-
E.
definesCommand
Indicates that one entity specifies or establishes a command that another entity can execute or obey.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:29 a.m.