Triple
T6482373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | newton |
E146424
|
entity |
| Predicate | inCGSSystem |
P32380
|
FINISHED |
| Object | 10⁵ dyne |
—
|
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: 10⁵ dyne | Statement: [newton, inCGSSystem, 10⁵ dyne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCGSSystem Context triple: [newton, inCGSSystem, 10⁵ dyne]
-
A.
rackSystem
Indicates a relationship where an entity functions as or belongs to a particular rack-based storage or mounting system.
-
B.
definesSystemAs
Indicates that one entity explicitly specifies or establishes another entity as the system to be used, referenced, or treated as authoritative.
-
C.
associatedSystem
chosen
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
D.
collisionSystem
Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
-
E.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6b2e9881908b715573e7ba7458 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:51 p.m.