Triple
T21627420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AY-3-8912 |
E533738
|
entity |
| Predicate | supportsEnvelopeGenerator |
P82800
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [AY-3-8912, supportsEnvelopeGenerator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEnvelopeGenerator Context triple: [AY-3-8912, supportsEnvelopeGenerator, true]
-
A.
hasEnvelopeGenerator
chosen
Indicates that an entity possesses or is associated with an envelope generator component that shapes the evolution of a signal or parameter over time.
-
B.
engagementEnvelope
Indicates the spatial or contextual bounds within which an interaction, operation, or engagement between entities is valid or permitted.
-
C.
launchEnvelope
Indicates initiating the sending or dispatching of an item or message, typically by packaging it into an envelope and starting its delivery process.
-
D.
supportsGeneration
Indicates that one entity enables, facilitates, or is compatible with the creation or production of another entity or outcome.
-
E.
enveloped
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52141e1c8190a861f4bc7cfcb490 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.