Triple
T31818855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien bridge oscillator |
E812208
|
entity |
| Predicate | bridgeHasArms |
P145091
|
FINISHED |
| Object | series RC arm |
—
|
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: series RC arm | Statement: [Wien bridge oscillator, bridgeHasArms, series RC arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeHasArms Context triple: [Wien bridge oscillator, bridgeHasArms, series RC arm]
-
A.
bridgeFeature
chosen
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
-
B.
bridgeOpened
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
-
C.
bridgeCarries
Indicates that a bridge serves as a route or support structure for transporting or conveying something (such as vehicles, pedestrians, or utilities) across an obstacle.
-
D.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
E.
hasSwingBridge
Indicates that one entity possesses or includes a swing bridge, i.e., a bridge section that can pivot or rotate to allow passage (typically of water traffic).
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6af7f24a881909e6ae0d937e90ea2 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:45 p.m.