Triple
T11265338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electricity and Magnetism |
E266669
|
entity |
| Predicate | usesFrameworkOf |
P9089
|
FINISHED |
| Object | special relativity |
—
|
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: special relativity | Statement: [Electricity and Magnetism, usesFrameworkOf, special relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFrameworkOf Context triple: [Electricity and Magnetism, usesFrameworkOf, special relativity]
-
A.
appliesFramework
chosen
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
-
B.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
C.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
D.
hasDistinctiveFrameworkWith
Indicates that one entity possesses a unique or distinguishing structural framework in relation to another entity.
-
E.
frameworkName
Indicates that a specific framework is identified by the given name.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94e5e3c8190a31995d55d20d7ed |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.