Triple
T3487931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poynting vector |
E73653
|
entity |
| Predicate | isUsedToDescribe |
P264
|
FINISHED |
| Object | energy transfer in electromagnetic waves |
—
|
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: energy transfer in electromagnetic waves | Statement: [Poynting vector, isUsedToDescribe, energy transfer in electromagnetic waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToDescribe Context triple: [Poynting vector, isUsedToDescribe, energy transfer in electromagnetic waves]
-
A.
isDescriptive
Indicates that one entity provides a description or characterization of another entity.
-
B.
isUsedToIllustrate
Indicates that one entity serves as an example or demonstration to clarify, explain, or represent another entity.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
E.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
- 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_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. |
Created at: March 8, 2026, 3:18 p.m.