Triple
T16501058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AM |
E400799
|
entity |
| Predicate | informationCarriedIn |
P96690
|
FINISHED |
| Object | variations in carrier amplitude |
—
|
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: variations in carrier amplitude | Statement: [AM, informationCarriedIn, variations in carrier amplitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationCarriedIn Context triple: [AM, informationCarriedIn, variations in carrier amplitude]
-
A.
dataCarried
chosen
Indicates that some data is transported, transmitted, or conveyed by a particular medium, channel, or entity.
-
B.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
containsDataAbout
Indicates that one entity holds or includes information or records pertaining to another entity.
-
E.
communicationsPayload
Indicates that an entity carries or contains equipment, data, or components specifically intended for communication purposes.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4ddc88819081fedb726add3e96 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.