Triple
T8035995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 858 |
E187108
|
entity |
| Predicate | definesOption |
P50557
|
FINISHED |
| Object | STATUS |
—
|
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: STATUS | Statement: [RFC 858, definesOption, STATUS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesOption Context triple: [RFC 858, definesOption, STATUS]
-
A.
commandOption
Indicates that one entity is a configurable command-line option or parameter associated with another command or executable.
-
B.
providesOption
chosen
Indicates that one entity makes a particular choice, alternative, or configuration available to another entity.
-
C.
commandLineOption
Indicates that one entity is a command-line option (a flag or parameter) used to modify the behavior of a command or program in relation to another entity.
-
D.
definesFlag
Indicates that one entity specifies or establishes a particular flag or boolean indicator used by another entity or process.
-
E.
configurationOptionIn
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef68c6081908727d17238b3522a |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.