Triple
T5085198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC5 |
E114618
|
entity |
| Predicate | parameter_w |
P12016
|
FINISHED |
| Object | word size in bits |
—
|
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: word size in bits | Statement: [RC5, parameter_w, word size in bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameter_w Context triple: [RC5, parameter_w, word size in bits]
-
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.
par
Indicates that two entities are parallel to each other in space or direction.
-
C.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
D.
materialParameter
Indicates a relationship where a specific parameter or property is associated with, or characterizes, a material in a given context.
-
E.
valueParity
Indicates that two compared values share the same parity (both even or both odd), or more generally, how a value’s parity is characterized in a given context.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd751db4f4819088b998d7af0e6f41 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.