Triple
T27841735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brans–Dicke theory |
E703697
|
entity |
| Predicate | hasParameterSymbol |
P133459
|
FINISHED |
| Object | ω |
—
|
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: ω | Statement: [Brans–Dicke theory, hasParameterSymbol, ω]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParameterSymbol Context triple: [Brans–Dicke theory, hasParameterSymbol, ω]
-
A.
hasParameter
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
-
B.
hasParameterType
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
-
C.
hasParameterization
Indicates that one entity serves as the specific parameterization or parameter-setting scheme used to define or configure another entity.
-
D.
hasSymbolFor
chosen
Indicates that one entity serves as the symbolic representation or sign for another entity.
-
E.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 6:03 p.m.