Triple
T2979675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | µA741 |
E80479
|
entity |
| Predicate | hasOutputStage |
P92
|
FINISHED |
| Object | class AB push-pull |
—
|
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: class AB push-pull | Statement: [µA741, hasOutputStage, class AB push-pull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputStage Context triple: [µA741, hasOutputStage, class AB push-pull]
-
A.
hasOutputStructure
Indicates that an entity produces, defines, or is associated with a particular structural form or arrangement as its output.
-
B.
hasOutputType
chosen
Indicates that an entity produces, returns, or yields a result of a specified type.
-
C.
hasStageProduction
Indicates that one entity is realized, adapted, or presented as a stage production (such as a play, musical, or theatrical performance) associated with another entity.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
hasStep
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999cca40819082e2d6d10bdb7872 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.