Triple
T7977066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6750 |
E185472
|
entity |
| Predicate | definesParameter |
P12016
|
FINISHED |
| Object | access_token |
—
|
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: access_token | Statement: [RFC 6750, definesParameter, access_token]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesParameter Context triple: [RFC 6750, definesParameter, access_token]
-
A.
parameter
chosen
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
C.
defaultParameterSet
Indicates that a particular set of parameters is designated as the standard or fallback configuration to be used when no other specific parameter set is provided.
-
D.
definesCommand
Indicates that one entity specifies or establishes a command that another entity can execute or obey.
-
E.
definesFlag
Indicates that one entity specifies or establishes a particular flag or boolean indicator used by another entity or process.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf716508190b4245bd5d89ae8c4 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.