Triple
T3487918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poynting vector |
E73653
|
entity |
| Predicate | isUsedToCompute |
P49064
|
FINISHED |
| Object | radiated power through a surface |
—
|
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: radiated power through a surface | Statement: [Poynting vector, isUsedToCompute, radiated power through a surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToCompute Context triple: [Poynting vector, isUsedToCompute, radiated power through a surface]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
isUsedToProbe
Indicates that one entity is employed as a tool or method to investigate, test, or explore the properties, behavior, or state of another entity.
-
D.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
E.
usedToInfer
Indicates that one entity serves as a basis or source from which another entity is logically derived or concluded.
- F. None of above. chosen
Provenance (4 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9193688190aa0cbf87a7b99446 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:18 p.m.